NSLOOKUP Problem

[jpollack]

Strange situation. The domain elitesettlementllc.com (216.247.177.19 Real IP). On occasion mail gets stuck in the queses intended for this domain. So, I started to think there might be a DNS issue. Using nslookup I typed elitesettlementllc.com and it returned 64.74.223.4 which is not the right IP after I verified everything via dnsstuff.com. After about ten minutes I tried nslookup against elitesettlementllc.com and this time the results were 216.247.177.19 which is correct. Here is the output from nslookup and ping. Why would the DNS server respond with the wrong IP and then correct it self?

Thanks,
John

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\administrator>nslookup elitesettlementllc.com
Server: 3ermsrv2.3ermlocal.3erm.com
Address: 192.168.1.2

Non-authoritative answer:
Name: elitesettlementllc.com
Address: 64.74.223.4


C:\Documents and Settings\administrator>ping -a 216.247.177.19

Pinging 216.247.177.19 with 32 bytes of data:

Reply from 216.247.177.19: bytes=32 time=28ms TTL=111
Reply from 216.247.177.19: bytes=32 time=26ms TTL=111
Reply from 216.247.177.19: bytes=32 time=144ms TTL=111
Reply from 216.247.177.19: bytes=32 time=32ms TTL=111

Ping statistics for 216.247.177.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 144ms, Average = 57ms

C:\Documents and Settings\administrator>ping -a 64.74.223.4

Pinging 64.74.223.4 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.74.223.4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\administrator>nslookup elitesettlementllc.com
Server: 3ermsrv2.3ermlocal.3erm.com
Address: 192.168.1.2

Non-authoritative answer:
Name: elitesettlementllc.com
Address: 216.247.177.19


C:\Documents and Settings\administrator>nslookup elitesettlementllc.com
Server: 3ermsrv2.3ermlocal.3erm.com
Address: 192.168.1.2

Non-authoritative answer:
Name: elitesettlementllc.com
Address: 216.247.177.19

 

[elgrandeperro]

The most likely cause is that one of the secondary servers for that domain has the wrong info. If you got a response from that server, you would get the cache the wrong info for TTL time. If the next time you get a 'good' response, it would correct itself.

gene