[TriLUG] DNS problems

[Rick DeNatale]

On 4/13/06, Brian Henning <brian at strutmasters.com> wrote:
> Hi Folks!
>    We just registered a domain in the .com.mx TLD.  Wahoo.  Here's the
> problem:
>
> Our current domestic web host provides our DNS for our
> strutmasters.com.mx domain name, and is properly configured:
>
> % dig www.strutmasters.com.mx @ns5.esosoft.net
> --snip--
> ;; ANSWER SECTION:
> www.strutmasters.com.mx. 43200  IN      CNAME   strutmasters.com.mx.
> strutmasters.com.mx.    43200   IN      A       161.58.166.59
> --snip--
>
> However, if I do a top-down dig of www.strutmasters.com.mx, I get:
>
> % dig www.strutmasters.com.mx
> --snip--
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10002
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;www.strutmasters.com.mx.       IN      A
>
> ;; AUTHORITY SECTION:
> com.mx.                 465     IN      SOA     a.ns.mx.
> hostmaster.nic.mx. 446764 3600 300 604800 1800
> --snip--
>
> (but if I dig for just strutmasters.com.mx, I get the correct authority
> section:
> ;; AUTHORITY SECTION:
> strutmasters.com.mx.    41836   IN      NS      ns5.esosoft.net.
> strutmasters.com.mx.    41836   IN      NS      ns6.esosoft.net.
> strutmasters.com.mx.    41836   IN      NS      ns7.esosoft.net.
> )
>
>
> That smells to me (a complete novice in the DNS world) like the .com.mx
> TLD authority (a.ns.mx) is misconfigured and doesn't realize that
> *.strutmasters.com.mx should fall to the same authority as
> strutmasters.com.mx.

I think that what it really means is that you've got a default dns
server which has cached an entry before your domain got to the tld
servers which hasn't expired yet.

If I look for www.strutmasters.com.mx I get:

$ dig www.strutmasters.com.mx
---snip---
;; QUESTION SECTION:
;www.strutmasters.com.mx.       IN      A

;; ANSWER SECTION:
www.strutmasters.com.mx. 42859  IN      CNAME   strutmasters.com.mx.
strutmasters.com.mx.    42859   IN      A       161.58.166.59

;; AUTHORITY SECTION:
strutmasters.com.mx.    42859   IN      NS      ns7.esosoft.net.
strutmasters.com.mx.    42859   IN      NS      ns5.esosoft.net.
strutmasters.com.mx.    42859   IN      NS      ns6.esosoft.net.

;; ADDITIONAL SECTION:
ns5.esosoft.net.        56208   IN      A       38.118.200.5
ns6.esosoft.net.        56208   IN      A       38.118.200.6
ns7.esosoft.net.        55992   IN      A       66.159.208.230

So I'd look closer to home for the problem.  Are you running a local
caching name server?  Had you done a lookup of www.strutmasters.com.mx
which failed earlier?

If you can't get whatever upstream dns server to flush the cache, the
solution might be just to wait for the cache entry to expire.

--
Rick DeNatale

Visit the Project Mercury Wiki Site
http://www.mercuryspacecraft.com/