This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] [UDM] Cannot select "recursion desired" for DNS
- Previous message (by thread): [atlas] [UDM] Cannot select "recursion desired" for DNS
- Next message (by thread): [atlas] [UDM] Cannot select "recursion desired" for DNS
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Tue Jan 8 13:03:51 CET 2013
On Tue, Jan 08, 2013 at 10:11:25AM +0100, Antony Antony <antony at ripe.net> wrote a message of 26 lines which said: > It will be enabled in the next release, OK, thanks. > However, by default RD is enabled when querying probe's local > resolver. Yes, but I wanted to test public resolvers. > Also my experience is som resolvers ignore it; My experience with public resolvers does not match yours: Google Public DNS: without RD, serves only the data in the cache (otherwise, if not in cache, NOERROR,ANSWER=0) OpenDNS: without RD, always REFUSED, even if data in the cache Level 3: like OpenDNS Comodo: like Level 3 and OpenDNS DNS Advantage: without RD, always timeout, even if data in the cache Telecomix: like DNS Advantage Regular Unbound: without RD, serves only the data in the cache (otherwise, if not in cache, REFUSED) Regular BIND: without RD, serves only the data in the cache (otherwise, if not in cache, NOERROR,ANSWER=0 but with upward referral)
- Previous message (by thread): [atlas] [UDM] Cannot select "recursion desired" for DNS
- Next message (by thread): [atlas] [UDM] Cannot select "recursion desired" for DNS
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]