Re: can't resolve some addresses
Alex Efros <[email protected]>
| Newsgroups | gmane.network.djbdns |
|---|---|
| Organization | http://powerman.name/ |
| Message-ID | <[email protected]> |
Hi! On Sun, Apr 05, 2009 at 11:07:42PM -0400, Jeff King wrote: > dnscache will send with the RD bit set if you have FORWARDONLY set in > your environment. Can you check that it is disabled (and remember that > even setting FORWARDONLY=0 is not sufficient; it must not be defined at > all). Wow! # cat /service/dnscache/env/FORWARDONLY 0 # rm /service/dnscache/env/FORWARDONLY # sv t dnscache # dnsip google.com 209.85.171.100 74.125.67.100 74.125.45.100 # dnsip pause.cpan.org 195.149.117.110 # dnsip pause.perl.org 195.149.117.110 # dnsip releases.mozilla.org 129.101.198.59 149.20.20.5 202.177.202.154 128.61.111.9 131.188.12.212 64.50.238.52 155.98.64.83 204.152.184.196 204.246.0.136 204.152.184.113 64.50.236.214 64.50.236.52 156.56.247.196 Correct me if I wrong, it looks like dnscache behaviour was changed at some version (I'm using it from ~2001 with same configuration including FORWARDONLY=0) and now to resolve using root dns servers instead of my ISP's dns servers I have to delete FORWARDONLY instead of setting it to 0? -- WBR, Alex.