-
Notifications
You must be signed in to change notification settings - Fork 30
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
Setting invalid options in /etc/resolv.conf makes dns unresponsive #418
Comments
aleksanderdidriksen
changed the title
Setting invalid options on host in /etc/resolv.conf makes dns unresponsive
Setting invalid options in /etc/resolv.conf makes dns unresponsive
Dec 11, 2023
in some ways, a strong argument could be made that it is behaving as designed ... but it would be nice to be more graceful. @aleksanderdidriksen are you interested in creating a PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you set invalid options in /etc/resolv.conf aardvark-dns will be unresponsive. It will run, but does not give any error even with RUST_LOG=trace
Note: these options are from Oracle Solaris and setting these options on a RHEL-based OS will not prevent DNS requests.
This is an example file: /etc/resolv.conf
aardvark-dns starts:
However, it does not respond to any queries:
No errors or anything about it found in syslog:
If you remove the bogous options from the /etc/resolv.conf file it works again. E.g. with this /etc/resolv.conf it will respond to queries as expected:
Tested:
aardvark-dns 1.7.0 (Podman package RHEL-based)
aardvark-dns 1.9.0 (Github Releases)
The text was updated successfully, but these errors were encountered: