resolv.conf #1190

New issue

Closed

opened 2026-03-16 01:52:06 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 01:52:06 +03:00

Owner

Originally created by @paul-palmer on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3478

Describe the bug
When /etc/resolv.conf contains an "option" line that includes the "no-aaaa" option, an error is returned.

To Reproduce
Add "no-aaaa" to the option line in /etc/resolv.conf

Expected behavior
Ideally, the code should honor no-aaaa and not query for IPv6 addresses during lookups. Minimally, it should at least not return an error on this valid option.

System:

OS: Linux
Architecture: x86_64
Version CentOS Stream release 9
rustc version: [e.g. 1.28]

Version:
Crate: resolver
Version: 0.25.2

Additional context
Add any other context about the problem here.

Originally created by @paul-palmer on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3478 **Describe the bug** When /etc/resolv.conf contains an "option" line that includes the "no-aaaa" option, an error is returned. **To Reproduce** Add "no-aaaa" to the option line in /etc/resolv.conf **Expected behavior** Ideally, the code should honor no-aaaa and not query for IPv6 addresses during lookups. Minimally, it should at least not return an error on this valid option. **System:** - OS: Linux - Architecture: x86_64 - Version CentOS Stream release 9 - rustc version: [e.g. 1.28] **Version:** Crate: resolver Version: 0.25.2 **Additional context** Add any other context about the problem here.

kerem closed this issue

2026-03-16 01:52:11 +03:00

kerem commented

2026-03-16 01:52:17 +03:00

Author

Owner

@djc commented on GitHub (Mar 3, 2026):

What error is returned?

@djc commented on GitHub (Mar 3, 2026): What error is returned?

kerem commented

2026-03-16 01:52:22 +03:00

Author

Owner

@paul-palmer commented on GitHub (Mar 3, 2026):

The error is: "Error parsing resolv.conf: option at line 4 is not recognized"

The full line from /etc/resolv.conf in question is: "options single-request no-aaaa rotate"

Removing "no-aaaa" prevents the error (but causes other difficulties in our environment).

@paul-palmer commented on GitHub (Mar 3, 2026): The error is: "Error parsing resolv.conf: option at line 4 is not recognized" The full line from /etc/resolv.conf in question is: "options single-request no-aaaa rotate" Removing "no-aaaa" prevents the error (but causes other difficulties in our environment).

kerem commented

2026-03-16 01:52:27 +03:00

Author

Owner

@djc commented on GitHub (Mar 3, 2026):

What Cargo.lock file are you building this with? If you use the latest version of resolv-conf (which should be semver-compatible), at least the parsing will work:

https://github.com/hickory-dns/resolv-conf/releases/tag/v0.7.5

@djc commented on GitHub (Mar 3, 2026): What `Cargo.lock` file are you building this with? If you use the latest version of resolv-conf (which should be semver-compatible), at least the parsing will work: https://github.com/hickory-dns/resolv-conf/releases/tag/v0.7.5

kerem commented

2026-03-16 01:52:32 +03:00

Author

Owner

@paul-palmer commented on GitHub (Mar 4, 2026):

That was a great question. The Cargo.lock is pinned to 0.7.0! I have asked the project maintainers to update to the latest version. For me, this issue is now resolved. Thank you for your assistance.

@paul-palmer commented on GitHub (Mar 4, 2026): That was a great question. The Cargo.lock is pinned to 0.7.0! I have asked the project maintainers to update to the latest version. For me, this issue is now resolved. Thank you for your assistance.

kerem referenced this issue

2026-03-16 05:18:23 +03:00

[PR #1190] [CLOSED] Flat name #2065