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'm trying to add a custom domain to an Azure Web Site in standard mode. I've added the following DNS records:

@                     IN  A
www                   IN  CNAME
awverify              IN  CNAME
awverify.www          IN  CNAME

Azure keeps telling me that it cannot find my CNAME record. It has been several hours since I made this change. Is azure's internal DNS caching really that slow, or have I made a typo somewhere that I'm not seeing?

Edit: Several hours later, still no dice. This has got to be an issue with azure websites, no? I can't figure out what the hell is wrong.

share|improve this question
Can you do the lookup yourself? Typos and caching are not the only two possibilities. – Ladadadada Dec 19 '13 at 21:31
Yes, I can do the lookup just fine. It appears to resolve fine in all cases. – Chris Dec 19 '13 at 22:27
up vote 1 down vote accepted

I was finally able to add the domain today. Apparently it really was just a cached records issue.

share|improve this answer
DNS is cached in many places and it can take several hours to replicate. I've seen this take anything from 5-10 minutes to a day. – Yossi Dahan Dec 23 '13 at 13:37
Yeah I'm well aware of that. I usually give it 24 ~hours. This one too almost 3 full days to replicate, however. – Chris Dec 23 '13 at 18:50

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.