disable synthesized hostname in systemd-resolved #3451
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
N/A - reported by @etungsten
Description of changes:
Disable the synthesized hostname feature in
systemd-resolved
.Otherwise, the reverse lookup in
netdog
will return "linux" if no other name can be resolved by DNS. This causes problems when trying to join several nodes to a Kubernetes cluster, since they all attempt to register as "linux".The expected (historical) behavior is that the system hostname winds up as the primary interface's IP address in this case. This is not ideal and causes other headaches: for example, the short name of the host is the first part of the IP in dotted decimal notation. But in the absence of a setting or reverse DNS, it's at least a potentially predictable and unique identifier.
Testing done:
Before:
After:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.