Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We added a second Web server to our network. I moved one of our Web sites to the new Web server. The old Web server has an external IP and has not changed. I went to our domain registrar and changed the external IP number of the Web site that was moved. Outside of our network the moved Web site displays correctly, but inside the network the DNS server does not resolve the web address. Our local domain controller is Windows Server 2008 Core. What do I have to do to get the domain controller to pick up on the change? I have tried rebooted and ipconfig /flushdns.

I should also mention that the resolves to the old internal IP address but returns 'could not find host'.

share|improve this question
What's up with the -1? – tony95 May 2 '12 at 19:44
up vote 0 down vote accepted

is the internal and external domain name the same? Meaning is your AD domain the same as your external? If so, you'll need to manually update the www record in DNS internally to the new IP.

If they are separate, you can flush the DNS cache on the server, and then do an nslookup on the server to verify it is getting the right IP from the correct DNS server that you are forwarding external lookups to.

share|improve this answer
No, they are different. The web site is and our domain is How do I flush the DNS cache on server? I did a ipconfig /flushdns. Needless to say, I am new at this. – tony95 May 2 '12 at 17:02
ON the DC, inside DNS admin, right click server, clear cache. Also post an NSLOOKUP output from the server itself here (masking the IPs and names), do an "nslookup" and post the masked results. – TheCleaner May 2 '12 at 17:06
This is a server core installation. Not sure what to do with it. – tony95 May 2 '12 at 17:07
>nslookup Server: Address: Name: >nslookup Server: Address: Name: Addresses: Aliases: – tony95 May 2 '12 at 17:13
Sounds like you might be using your internal DNS server as authoritative for the external domain as well. You'll need to load up DNS admin tools and connect to the w2k8 dns server. Then change the entries in DNS to the new IP (whether resolving to the new external or new internal is based on how it is currently setup). – TheCleaner May 2 '12 at 17:17

Check your hosts file - the site/IP may be hard-coded.


Open the file in notepad.

share|improve this answer

Your Answer


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.