[lug] Weird DNS problems

[Chip Atkinson]

Jeez.  I don't know how many times I over looked that.  I'll make the 
changes there.  Thanks for the guidance.  Hopefully that will get things 
fixed up a bit.

Chip

Hugh Brown wrote:

> whois returns that pupman is registered with the old ip address.  It looks
> you need to go to your registrar and get them to update the record.
> 
> Hugh
> 
> 
> "Chip Atkinson"
> 
>> I believe that jymis.com has the authoritative domain records.  That 
>> what dig seems to indicate:
>> 
>> ;; AUTHORITY SECTION:
>> pupman.com.             16h25m42s IN NS  ns1.jymis.com.
>> pupman.com.             16h25m42s IN NS  ns0.jymis.com.
>> 
>> AAARGHHH!!! Ok, I think this is the problem:
>> 
>>  > server G.GTLD-SERVERS.NET
>> Default Server:  G.GTLD-SERVERS.NET
>> Address:  192.42.93.30
>> 
>>  > pupman.com
>> Server:  G.GTLD-SERVERS.NET
>> Address:  192.42.93.30
>> 
>> Non-authoritative answer:
>> Name:    pupman.com
>> Address:  199.45.150.249
>> 
>> (The 199.45... address is old and out of date)  It should be 63.173.117.115.
>> 
>> Ok, how did you resolve the problem?
>> 
>> Thanks for the advice.
>> 
>> Chip
>> 
>> Hugh Brown wrote:
>> 
>> 
>>> A couple of thoughts.  Who is authoritative for your domain?  If it is the
>>> qwest servers, do you know for sure that they updated the tables on the
>>> bogus server?
>>> 
>>> I have had the problem with DNS if the root name servers have one ip and
>>> the authoritative dns server for the domain have different ip's then things
>>> go a little screwy.
>>> 
>>> Hugh
>>> 
>>> "Chip Atkinson"
>>> 
>>> 
>>>> Greetings,
>>>> 
>>>> I'm having some domain lookup problems that I can't seem to figure out 
>>>> and was hoping that someone could help me or at least point me in the 
>>>> right direction.
>>>> 
>>>> Here's the original problem:
>>>> Mail from a mailing list that I run was producing an error when sent to 
>>>> a subscriber at qwest.net.  It is "stat=Data format error" and "DSN: 
>>>> Data format error".  A little search on the web indicated it might be a 
>>>> DNS problem. (Yes, it is DSN in the error).
>>>> 
>>>> I go to the name servers listed in /etc/resolv.conf and try to do a 
>>>> forward and reverse lookup of my domain, pupman.com.
>>>> 
>>>> $ cat /etc/resolv.conf
>>>> search pupman.com
>>>> nameserver 206.196.128.1
>>>> nameserver 204.147.80.5
>>>> (both are Qwest's name server as I send the mail out through a DSL 
>>>> connection via them.)
>>>> 
>>>> Forward lookups of pupman.com work on the 206 server works, but the 204 
>>>> server has an old IP from around August.  Reverse lookups don't seem to 
>>>> work at all.
>>>> 
>>>> Does anyone know what's going on?  I thought that name servers got the 
>>>> information from the name server listed in the whois record.  This 
>>>> doesn't seem to be the case to me becaue it's been since Aug. when I 
>>>> used the old IP and one would think that the cache at Qwest's name 
>>>> servers would have expired.  Furthermore, if I set q=any and query the 
>>>> server giving the bogus results it seems to use the right name server 
>>>> from the whois records.
>>>> 
>>>> I'm stumped right now.
>>>> Thanks in advance for any help.
>>>> 
>>>> Chip
>>> 
>>> _______________________________________________
>>> Web Page:  http://lug.boulder.co.us
>>> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>> 
>> _______________________________________________
>> Web Page:  http://lug.boulder.co.us
>> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>> 
> 
> 
> ------------------------------------
> System Administrator/Unix Consultant
> hugh at vecna.com
> Vecna Technologies, Inc
> 6525 Belcrest Rd, Suite 612
> Hyattsville MD, 20782
> 301.864.7253
> http://www.vecna.com
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug