DNS bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

There is problem in pjproject handling SERVFAIL responses from the 
nameserver. Obviously, if a nameserver responds several times with 
SERVFAIL, the NS get marked as bad. This is wrong, as the nameserver 
might be good - it it is just an upstream error.

e.g. take a look at the attached 2 traces. I started pjsua to register a 
at a SIP proxy. In one case, the used STUN server has a broken domain 
configuration, thus the resolver responds with SERVFAIL. This marks the 
nameserver as broken and the following DNS lookup for the SIP domain is 
not even tried, as the nameserver is tagged as broken!

Conclusion: A nameserver must not be tagged as "nonworking" just because 
of received SERVFAIL - as this might be caused by an upstream problem.

regards
Klaus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bad.txt
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090828/15c2fa89/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: good.txt
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090828/15c2fa89/attachment-0001.txt>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux