On Tuesday, August 17, 2004, 1:42:13 AM, Raymond Dijkxhoorn wrote: (Dave Burke wrote:)
I think it's to do with which nameserver you get back. I noticed when I switched mine to rbldnsd that other day that I was unable to resolve www.surbl.org from it anymore...
dave@pagh:~$ dig version.bind chaos txt @ns16.surbl.org +short "rbldnsd" dave@pagh:~$ dig a www.surbl.org @ns16.surbl.org +short dave@pagh:~$ dig version.bind chaos txt @ns14.surbl.org +short "rbldnsd 0.992 (7 Mar 2004)" dave@pagh:~$ dig a www.surbl.org @ns14.surbl.org +short dave@pagh:~$ dig version.bind chaos txt @ns13.surbl.org +short "8.3.7-REL" dave@pagh:~$ dig a www.surbl.org @ns13.surbl.org +short 66.170.2.60
Your RBLDNSD should not be listed as authorative server for the main zone, only for the subzones... They can only answer for the zones you loaded.
But since 'only' NS1-13 are used for the SURBL.ORG zone this wont afect anything, unless you also forward (locally) your requests or surbl.org to that RBLDNSD...
Jeff is checking is we have servers 1-16 all ok now. So we can exclude that from any problemlist shortly :)
Yes, I just took ns16 out of the delegations for the parent zone. All the authoritative servers for the parent zone should be ok now.
Dave, if you were trying to load surbl.org in rbldnsd, please take that out. As Raymond says the rbldnsd servers should be loading only the subdomains.
Jeff C.