discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
Re: [opennic-discuss] simple question, when using a private caching/resolving DNS server
Chronological Thread
- From: "Walter H." <Walter.H AT mathemainzel.info>
- To: discuss AT lists.opennicproject.org
- Subject: Re: [opennic-discuss] simple question, when using a private caching/resolving DNS server
- Date: Thu, 9 Apr 2020 14:15:15 +0200
- Dkim-filter: OpenDKIM Filter v2.11.0 vhost01.ipv6help.de 07E7E63D50
- Organization: Home
Hello,
ok, when a DNS-rquest of an ICANN entrie is done,
does this go no slower than 'now'?
e.g. doing
nslookup www.vienna.at
on my windows box, using my DNS cache/resolver
I'm new to this alternative DNS; when replacing the root.hints,
do I have to trust the OpenNIC DNS servers with the ICANN entries
or does my cache/resolver still do the DNSSEC validation of the ICANN entries?
Thanks,
Walter
On 08.04.2020 00:28, Jeff Taylor wrote:
No, you wouldn't append it to your root.hints, you would use that output to completely replace your root.hints. Opennic's root zone also carries ICANN entries, so you have full access when using our DNS servers.
On 04/03/2020 02:48 AM, Walter H. wrote:
Hello,
I found here a guide
https://philly2600.net/articles/bypass-your-isps-dns/
how to configure BIND;
at this step
|dig . NS @75.127.96.89 > /etc/bind/db.root|
|can this be just appended to the root.hints of a non-OpnenNIC-DNS-Server?|
|would there be DNS requests faster?
|
|Thanks,|
|Walter
|
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-
[opennic-discuss] simple question, when using a private caching/resolving DNS server,
Walter H., 04/03/2020
-
Re: [opennic-discuss] simple question, when using a private caching/resolving DNS server,
Jeff Taylor, 04/08/2020
- Re: [opennic-discuss] simple question, when using a private caching/resolving DNS server, Walter H., 04/09/2020
-
Re: [opennic-discuss] simple question, when using a private caching/resolving DNS server,
Jeff Taylor, 04/08/2020
Archive powered by MHonArc 2.6.19.