up vote 0 down vote favorite
share [g+] share [fb]

When a certain NS gets asked "what's the A of sipfs02.example.com?" it gives back the RR I need. But if I ask first for "the AAAA of sipfs02.example.com", it gives back an NXDOMAIN instead of NOERROR. And then the NXDOMAIN gets cached for the following query.

I'm running bind9. I searched for DNS AAAA and BIND AAAA, but got no interesting results. Got one about patching djbdns to "poison" all NXDOMAINs, but I want to kick only one particular server, not everyone.

Thanks!

link|improve this question
1  
That certain NS is broken and you should notify the DNS admins for that domain that it is. It should be returning NOERROR. – Mark Wagner Aug 13 '10 at 17:34
Yes, I agree! Unfortunately, the DNS admins aren't responsive. Even better, sipfs01.example.com does NOT exhibit this behaviour. This is why I'm planning on poisoning the RR and workaround their bug. – Luis Bruno Aug 24 '10 at 14:46
1  
So just block communication with sipfs02.example.com? :> – al. Oct 11 '10 at 14:31
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.