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

I really don't understand why I'm experiencing so much trouble for just creating a simple dns entry for myself. I have a Windows 2003 Server that is a Domain Controller and the DNS Server. This server has 2 ips 192...10 and 192...6. There are Host (A) records setup for 192...10 using which correctly resolves to 192...10.

When I try to create an Alias (CNAME) record that points to the FQDN of nothing occurs.

If I create an Host (A) record for 192...6 while inside the DNS server I can run

nslookup 192...6 and it will return

however if I nslookup once again it resolves to nothing.

share|improve this question
up vote 2 down vote accepted

Try running ipconfig /flushdns. I've seen that fix alot of weird DNS issues.

share|improve this answer
192 is a private IP anyway. No harm in posting the actual full internal address for the most concise answer. – MDMarra Jul 23 '09 at 21:28
The first 3 octets are all the same, I thought it would be easier to read not having an extra 10 octects of numbers in my post that offer no meaning. – Chris Marisic Jul 24 '09 at 15:13
FlushDNS seemed to work it's picking up the forward lookup now and I can actually use it, thanks! – Chris Marisic Jul 24 '09 at 15:31
@Chris Marisic: Glad it worked for you. Even though they are all the same ... when you are used to seeing formatting at least for me the 192...1 just makes it harder to read. – Zypher Jul 24 '09 at 15:44

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.