>The issue is specific to his domain, since I use Savvis for my backbone, I
>thought it best to check, and everything is fine for my block 209.144.1.0/24
>in both servers.
Actually, it doesn't seem specific to his domain. It's specific to all
Savvis reverse DNS entries in the 216.88.0.0/16 Class B range, and quite
possibly more than that.
ns1.savvis.net and ns2.savvis.net both have the same serial number for the
88.216.in-addr.arpa. zone. That means that they claim to have the
identical data. Yet the two servers are returning different data. Either
one of them has corrupt data, or Savvis changed the data in the zone
without updating their SOA serial number (which isn't allowed). Either
way, the data in their two DNS servers are not synchronized, and in either
case, it could well affect other zones on Savvis DNS servers.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
