-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove networking.hostConf option #74032
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# Test whether DNS resolving returns multiple records and all address families. | ||
import ./make-test-python.nix ({ pkgs, ... } : { | ||
name = "resolv"; | ||
meta = with pkgs.stdenv.lib.maintainers; { | ||
maintainers = [ ckauhaus ]; | ||
}; | ||
|
||
nodes.resolv = { ... }: { | ||
networking.extraHosts = '' | ||
# IPv4 only | ||
192.0.2.1 host-ipv4.example.net | ||
192.0.2.2 host-ipv4.example.net | ||
# IP6 only | ||
2001:db8::2:1 host-ipv6.example.net | ||
2001:db8::2:2 host-ipv6.example.net | ||
# dual stack | ||
192.0.2.1 host-dual.example.net | ||
192.0.2.2 host-dual.example.net | ||
2001:db8::2:1 host-dual.example.net | ||
2001:db8::2:2 host-dual.example.net | ||
''; | ||
}; | ||
|
||
testScript = '' | ||
def addrs_in(hostname, addrs): | ||
res = resolv.succeed("getent ahosts {}".format(hostname)) | ||
for addr in addrs: | ||
assert addr in res, "Expected output '{}' not found in\n{}".format(addr, res) | ||
|
||
|
||
start_all() | ||
resolv.wait_for_unit("nscd") | ||
|
||
ipv4 = ["192.0.2.1", "192.0.2.2"] | ||
ipv6 = ["2001:db8::2:1", "2001:db8::2:2"] | ||
|
||
with subtest("IPv4 resolves"): | ||
addrs_in("host-ipv4.example.net", ipv4) | ||
|
||
with subtest("IPv6 resolves"): | ||
addrs_in("host-ipv6.example.net", ipv6) | ||
|
||
with subtest("Dual stack resolves"): | ||
addrs_in("host-dual.example.net", ipv4 + ipv6) | ||
''; | ||
}) |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we add an
/etc/host.conf
with this value by default?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Will update the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
host.conf
honoured in thensswitch.conf
world?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICT yes as long as you use glibc's resolver directly. It might by another story when using dnsmasq or systemd-resolvd .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should happen inside the
file
part ofnsswitch.conf
, so before and regardless of which resolver is used to do DNS lookups.For context, this was introduced during #19148, and seems to be the default on ArchLinux.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flokli I've studied the man pages but got still no clue about how this should be expressed in nsswitch.conf. Could you provide an example?