strange cacheing results

[Cricket Liu]

> I'm running bind 8.3.3 (straight compile) on solaris 8 boxes.=20
>
> On Saturday, I recieved notification that my west coast dns servers were =
> unable to resolve a couple of domains.  I did nslookups on each and got =
> a non-existent host/domain after a long time period.  Same results with =
> a dig.  I checked my east coast servers and they were able to resolve =
> fine. So, I did a namedb dump from ndc and searched for the domains.  =
> The results were below.
>
> dbkassociates   2978    IN      NS      NS8.SAN.YAHOO.COM.      =
> ;Cr=3Daddtnl [209.173.58.65]
>         2978    IN      NS      NS9.SAN.YAHOO.COM.      ;Cr=3Daddtnl =
> [209.173.58.65]

I think this entry is for dbkassociates.biz, not dbkassociates.com, since
the referring name server was a .biz name server.

> geranen 90170   IN      NS      NS1.MYDOMAIN.com.       ;Cr=3Daddtnl =
> [192.12.94.30]
>         90170   IN      NS      NS2.MYDOMAIN.com.       ;Cr=3Daddtnl =
> [192.12.94.30]
>         90170   IN      NS      NS3.MYDOMAIN.com.       ;Cr=3Daddtnl =
> [192.12.94.30]
>         90170   IN      NS      NS4.MYDOMAIN.com.       ;Cr=3Daddtnl =
> [192.12.94.30]

This cached data looks fine.  Did you see any negative cache entries?
What domain names were your West Coast name servers unable to resolve?

> below is what i get from the east coast servers using nslookup
>
> dbkassociates.com
>         origin =3D no-dyn-updates.san.yahoo.com
>         mail addr =3D postmaster.san.yahoo.com
>         serial =3D 2002093001
>         refresh =3D 10800 (3H)
>         retry   =3D 3600 (1H)
>         expire  =3D 7084000 (7084000)
>         minimum ttl =3D 300 (5M)
> dbkassociates.com       nameserver =3D ns8.san.yahoo.com
> dbkassociates.com       nameserver =3D ns9.san.yahoo.com
> ns8.san.yahoo.com       internet address =3D 209.132.1.27
> ns9.san.yahoo.com       internet address =3D 209.132.2.27
>
> geranen.com
>         origin =3D ns1.mydomain.com
>         mail addr =3D hostmaster.geranen.com
>         serial =3D 1033406041
>         refresh =3D 16384 (16384)
>         retry   =3D 2048 (2048)
>         expire  =3D 1048576 (1048576)
>         minimum ttl =3D 2560 (2560)
> geranen.com     nameserver =3D ns1.mydomain.com
> geranen.com     nameserver =3D ns2.mydomain.com
> geranen.com     nameserver =3D ns3.mydomain.com
> geranen.com     nameserver =3D ns4.mydomain.com
> ns1.mydomain.com        internet address =3D 216.148.213.141
> ns2.mydomain.com        internet address =3D 216.148.221.142
> ns3.mydomain.com        internet address =3D 216.148.213.143
> ns4.mydomain.com        internet address =3D 216.148.221.144
>
> I was able to resovle other addresses (like yahoo.com, cnn.com, etc).
> I didn't see anything else wrong so I restarted ndc and was then able to =
> resolve the addresses.
>
> Does any know what could have caused the lookups to fail?  I've had this =
> happen a couple of times (more so when I was using version 8.2.5 of =
> bind).

I don't see any indication of why the West Coast name servers' name
resolution failed.

cricket

Men & Mice
DNS Software, Training and Consulting
www.menandmice.com

The DNS and BIND Cookbook, coming October 2002!
http://www.oreilly.com/catalog/dnsbindckbk/