On Sun, 6 Sep 2009, Leen Besselink wrote: >>> $ dig +short +norec @l.gtld-servers.net. ns2.titan.net. >>> 64.13.134.59 >>> >>> Hope this was helpful. >> >> Are you sure you dont just have different settings for harden-glue >> or harden-referral-path? See if you can see the same difference >> when resolving an NS record for www.rbc.com (a site known to be >> reachable through trusting glue) > Changing those settings doesn't matter a thing. You can try those > domains on your recursive DNS, if you like. :-) Well, for me both ns1.titan.net. and ns2.titan.net, which are NS for both titan.net and insecure.org are unreachable. Both are in the same /24 too. I guess Fyodor needs a DNS admin :P I'd still still you were seeing some caching on one instance of unbound that the other instance just did not have. Paul