How to get the latest DNS settings?

[Guest]

Hi,

I have the following trouble with two machines on our network:

I want to access a website that recently has changed hosts. Although my
Linksys router is correctly tracing to the new IP address, the machine itself
still goes to the old one.
All tricks like IPCONFIG/FLUSHDNS, deleting temp. Internet files or 'always
get the latest version of the website' have not been successfull.

Anybody got another idea?


Thanks

 

[Ron Lowe]

Hi,

I have the following trouble with two machines on our network:

I want to access a website that recently has changed hosts. Although my
Linksys router is correctly tracing to the new IP address, the machine
itself
still goes to the old one.
All tricks like IPCONFIG/FLUSHDNS, deleting temp. Internet files or
'always
get the latest version of the website' have not been successfull.

Anybody got another idea?


Thanks

Probably a caching issue. It will most likely fix itself once the
changes have propogated around the DNS system.
But you can check it out manually.

You didn't give the name of the site you are having problems with,
so I can't check it's DNS status for you.

Go here: http://www.dnsstuff.com/ In the top right, ( 'DNS Lookup' ); enter
the page URL , leave the Record Type set to 'A', and hit 'Lookup'. Are the
results correct? If not, your hosting company has not updated your DNS
correctly and you need to get onto them.

If that gave the correct result, then the DNS records are correctly
published, and you need to look at your local name resolution.

First, check your local HOSTS file does not have a stale entry in it.
If so, remove the offending line from Hosts.

Then use NSLOOKUP to query your local / ISP DNS servers to check whether
they have stale records.
If NSLookup reposts the wrong answer, double-check you are pointing to the
correct DNS server, and contact the DNS server admin to have the stale
record removed. It should remove itself in due course, once the record TTL
expires.

Here's a sample nslookup session:

C:\Documents and Settings\Ron.HOMENET>nslookup
Default Server: homenetdc02.homenet.local
Address: 81.187.191.78 <- Check it is using the DNS server you expect.

www.google.com <- Type the name of the web page you are trying.

Server: homenetdc02.homenet.local
Address: 81.187.191.78

Non-authoritative answer:
Name: www.l.google.com
Addresses: 216.239.59.104, 216.239.59.99, 216.239.59.147, 216.239.59.103
Aliases: www.google.com

exit <- Exit to leave the program.

C:\Documents and Settings\Ron.HOMENET>

 

[Yves Leclerc]

Hi,

I have the following trouble with two machines on our network:

I want to access a website that recently has changed hosts. Although my
Linksys router is correctly tracing to the new IP address, the machine itself
still goes to the old one.
All tricks like IPCONFIG/FLUSHDNS, deleting temp. Internet files or 'always
get the latest version of the website' have not been successfull.

Anybody got another idea?


Thanks

The problem is that your ISP DNS has not gotten the new IP address for the web
page. Since you stated that the web page has changed "hosts", the IP address
is likely to have changed. Depending on the wep page host's DNS management,
the DNS IP address update can take 48 to 72 hours to be sent out across the
Internet. Just wait for it.

 

[Yves Leclerc]

The problem is that your ISP DNS has not gotten the new IP address for the web
page. Since you stated that the web page has changed "hosts", the IP address
is likely to have changed. Depending on the wep page host's DNS management,
the DNS IP address update can take 48 to 72 hours to be sent out across the
Internet. Just wait for it.

Make that web instead of wep.

 

[Guest]

Hi Ron,

thanks for your posting. As the DNS settings had already reached my router
(I tracerouted the domain in my router to the new IP address), it was clear
to me that neither my host nor my ISP were responsible. I flushed the DNS
cache of the machine, switched it off and this morning -voila- the machine
went for the new server. Browsing through microsoft.com I found an article
that mentioned to stop the DNS Client Service so that the machine does not
look any DNS up in its cache. I guess that one would have been the right way
to proceed.
But thanks anyway! I now learned about nslookup...