dns MX caching issue

[Danny Mayer]

The last time I looked, within the last week, interland.net had major
configuration problems.  This makes it look like the situation hasn't
changed.

         Danny
At 01:56 AM 2/14/02, Michael Harris wrote:

>Hi,
>I have done a good deal of searching on this issue but alas must
>turn to the world forum to get an answer. We run a fax to email
>service
>and have had chronic problems delivering to the domain
>worthfunding.com
>but I cannot tell precicely why. What I see happening is we can
>resolve
>their MX for an hour or so and then cannot, and a restart of my name
>server
>fixes the problem until it occurs again. I am running bind-9.1.0-10
>and deliver tens of thousands of emails per day resolving using the
>same server. When it occurs a cache dump shows no MX entry for the
>domain,
>and after a server restart and a lookup the MX is listed in the cache.
>
>A whois on the domain lists the following as registered dns servers
>(on network solutions):
>    DNS1.INTERLAND.NET           64.224.20.132
>    DNS2.INTERLAND.NET           64.224.20.133
>
>however an SOA query to either of these servers for worthfunding.com
>turns
>up the following mismatch for NS records:
>
>[asphalt 124] dig -t soa worthfunding.com @64.224.20.132
>
>; <<>> DiG 9.1.0 <<>> -t soa worthfunding.com @64.224.20.132
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48180
>;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
>
>;; QUESTION SECTION:
>;worthfunding.com.              IN      SOA
>
>;; ANSWER SECTION:
>worthfunding.com.       900     IN      SOA     a.ns.interland.net.
>hostmaster.interland.net. 5 3600 4 604800 900
>
>;; AUTHORITY SECTION:
>worthfunding.com.       86400   IN      NS      a.ns.interland.net.
>worthfunding.com.       86400   IN      NS      b.ns.interland.net.
>worthfunding.com.       86400   IN      NS      c.ns.interland.net.
>
>;; ADDITIONAL SECTION:
>a.ns.interland.net.     900     IN      A       64.226.28.33
>b.ns.interland.net.     900     IN      A       66.111.73.173
>c.ns.interland.net.     900     IN      A       64.77.127.42
>
>;; Query time: 28 msec
>;; SERVER: 64.224.20.132#53(64.224.20.132)
>;; WHEN: Wed Feb 13 23:52:10 2002
>;; MSG SIZE  rcvd: 193
>----------------------
>
>So the NS records listed by this authoritative server does not include
>either
>of the registered authority servers. I do not know if/why this is a
>problem,
>but looking at several major ISP domains the servers listed always
>reconcile
>between the registration and that returned by the SOA to an authority.
>
>Also reverse lookups for 64.224.20.132 and 64.224.20.133 turn up
>www.autographplanet.com and nothing, respectively.
>
>Does this or anything about their listing jump out as a problem to
>anyone?
>
>Thanks in advance for any advice.
>Mike