Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I am in the process of moving from a linux webserver to a new Windows webserver, and I have been having trouble getting one of my sites to update and resolve to the new web server. To be honest I dont think I fully understand how DNS works. Below is my configuration, if you can provide pointers on how this should be configured to work correctly, then that would be great.

I have the domain mydomain.com, registered through Othello technologies. This is configured to use ns1.myname.com / ns2.myname.com, which is then registered through SimplyNames. I have configured ns1 / ns2 to resolve to the IP address of my new server, (registered through Webfusion) and indeed accessing ns1.myname.com in the web browser takes you to the correct web server. However, accessing mydomain.com still resolves to the old server.

I appreciate you cannot troubleshoot the problem from this information, but instead I would like to know how exactly each step should be set up in terms of NS/A records in order to correctly resolve in a situation where 3 different companies are used for registering and hosting the domains.

The Webserver is a Windows 2008 Server running plesk 10. Are there any additional configuration changes that need to be made in here in order to configure the server to run as a nameserver?

share|improve this question
    
What's the actual domain name so that we can give you real information as to what you need. –  joeqwerty Aug 13 '11 at 19:52
    
The actual domain is taxiwayalpha.com - although rather than looking for an answer as to how to fix this issue, I would like someone to point me to a good description of how DNS works and how it should be configured in this situation. –  Gavin Coates Aug 15 '11 at 8:38

2 Answers 2

NS1 and NS2 hold the zone for yourdomain.com, all queries to resolve hostnames for yourdomain.com are directed to those two servers to get a reply. You need to find out why NS1 and NS2 are answering the query for yourdomain.com with the old address, and then adjust the A record for that domain to point to the new IP address.

In short, you're confusing nameserver resolution with NAME resolution. The former is about finding who to ask about a domain, the latter about actually resolving a host in the domain.

share|improve this answer

If you are only migrating your web server, then the records specifically dealing with the web server (A and/or maybe CNAME) are typically the only ones needing any updates to reflect the new web server's IP. Typically no other DNS records/settings will need updating.

In addition, the DNS changes may take a little time to make it out across the Internet. Depending on the DNS update intervals and frequencies (which will vary across the DNS servers), it can take a day or so for the changes to make it across the entire public Internet.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.