• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 594
  • Last Modified:

How to refresh DNS-Adresses

I moved our web-application http://abcd.net to a new server with a different IP Adress (and added a little detail to distinguish responses from both servers)

We changed the DNS settings for http://abcd.net on our DNS Server yesterday.

Today...

Typing http://abcd.net in a browser (safari, IE, Firefox) on a client that never requested that URL http://abcd.net before gives user response from the new server.

Typing http://abcd.net in a browser ( safari, IE, Firefox) on a client that requested that URL before results in a response from the old server.

Both clients are in same LAN.

I have tried (sorry, translations may be not 100% correct)
- IE: Remove browser history (all checked)
- Safari: set back Safari (all checked)
- Firefox: delete chonicle (all checked)

...but still browsers on clients that recently requested http://abcd.net find URL http://abcd.net in IP-Adress of the old Server

What must be done that these clients also find http://abcd.net on the IP of the new server, like those clients who have not requested http://abcd.net before?

I need a solution because the next app that needs to be moved is a database application and it will not be possible to maintain 2 versions of that app on 2 servers.
 

Thanks for your hints
0
joachim58
Asked:
joachim58
3 Solutions
 
netballiCommented:
Try using Nslookup command to see what IP the URL http://abcd.net resolves to.

if you have more that one dns server you also have to confirm if they have replicated the record change between them to reflect the changed DNS settings.
0
 
John EastonDirectorCommented:
This is normal and should be expected when changing DNS addresses.

Most DNS server cache the results (usually for up to 24 hours) and therefore some clients will recieved these stored details until their DNS requeries the details.  Due to the structure of DNS it can take up to 48 hours for the information to propergate around the world's DNS servers.

I should note, a poorly configured DNS server may be set to refresh less frequently although this should be rare.
0
 
joachim58Author Commented:
Thank you, both have been good help, but I found solution here: C:\Windows\System32\drivers\etc\hists on the client that did not find the new adress pointet to the old adress...
0
 
ABCStoreCommented:
ipconfig /flushdns

will do the trick for you. Surprised it has not been answered earlier...
0
 
joachim58Author Commented:
It was the solution
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now