Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

another dns trouble

Status
Not open for further replies.

FALCONSEYE

Programmer
Jul 30, 2004
1,158
US
I was asked to move a site from server A to server B. The last step was to change the dns A record entry. Now that I changed the A record from xx.xxx.xxx.158 to xx.xxx.xxx.157,

I still cannot see the on the new server. When I ping from my local machine, I get the correct ip address of which: xx.xxx.xxx.157. On the other hand, when I ping the same domain from the server (.157/the dns server), I still get xx.xxx.xxx.158.

I did ipconfig /flushdns and even changed the TTL to 1min and still no luck. Does anybody know what I am doing wrong?
thanks

 
Ok, the problem was dns caching. I did two things: locally, ipconfig /flushdns and on the server:
Now, the next problem I have is that there are a ton of users already. So, how am i going to let every client do the flushdns thing? Is there an easier way of this?
thanks

 
If you had a long TTL before you changed it to 1 minute, then your windows machines are going to cache it for that period. Also, browser cache seems to always play havoc.

Always a good thing to do is REDIRECT from the old ip the new one ( at the server level). You can also record those ips that seem to use the old ip that way.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top