We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
hickory-dns
as far as I could tell the steps are:
cargo install hickory-dns --features recursor
create /etc/named.toml with the contents
/etc/named.toml
[[zones]] zone = "." zone_type = "Hint" stores = { type = "recursor", roots = "/etc/root.hints" }
In production, /etc/root.hints should be fetched from https://www.iana.org/domains/root/files
/etc/root.hints
Run hickory-dns
Check with dig @localhost A www.example.com.
dig @localhost A www.example.com.
It should be noted that, currently, DNSSEC validation is disabled and cannot be enabled.
if that sounds about right, I can submit a PR with the above information.
maybe some information about _cache_size should be included.
_cache_size
same for zone_type. should it ever be set to some other variant for this use case?
zone_type
The text was updated successfully, but these errors were encountered:
That looks about right. I did want to start spending some time laying out the book for giving direction like this.
Sorry, something went wrong.
No branches or pull requests
as far as I could tell the steps are:
cargo install hickory-dns --features recursor
create
/etc/named.toml
with the contentsIn production,
/etc/root.hints
should be fetched from https://www.iana.org/domains/root/filesRun
hickory-dns
Check with
dig @localhost A www.example.com.
It should be noted that, currently, DNSSEC validation is disabled and cannot be enabled.
if that sounds about right, I can submit a PR with the above information.
maybe some information about
_cache_size
should be included.same for
zone_type
. should it ever be set to some other variant for this use case?The text was updated successfully, but these errors were encountered: