On Monday, November 22, 2004, 1:13:17 PM, Dallas Engelken wrote: > I've been troubleshooting a system today that is having problems with > SA. It appears their DNS servers will not answer NS records, and only > [A] recoreds. A,MX,CNAME,SOA,PTR all work fine (strangest thing ever)... > So when SA starts up, the DNS detection code decides that DNs is not > available.
NS records are used by uridnsbl, by default against sbl.spamhaus.org. A records against SURBLs by urirhsbl and urirhssub. All three commands are in URIDNSBL.pm. I have not looked at the source code, but NS records should not be checked for SURBL lookups, just A records as you note. Perhaps there's some inappropriate code from uridnsbl being used by urirhssub, etc.? BTW, I wonder if this is related to the intermittent FP reports we get where people are seeing domains hit SURBLs when they're not actually listed and can't be listed. Perhaps NS records are being hit on SURBL lookups??? What platform experiences this odd behavior with not answering NS records? Perhaps we can correlate it with some of these FP reports. Jeff C.
