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

Call me an early adopter, but I recently migrated my web service over from an Azure web-role to a "Reserved instance" on their new web sites service (mainly for git deploy!).

The migration went smoothly, but I'm seeing strange downtime patterns, typically for 5 minutes every 30 minutes (not exact timings but +/- a few minutes). According to Pingdom, the problem is DNS resolution, not the Azure service itself.

I use ZoneEdit for my DNS, have the root domain forwarded to www. www is a CNAME record which used to be linked to (which worked fine), and is now

Is this DNS solution a good one? Should I be seeing this downtime? I understand that using A records directly is a bad idea due to reallocation of endpoints etc.


share|improve this question
What's your DNS TTL? It should probably be something tiny. – ceejayoz Jun 14 '12 at 17:27
It was actually the default really large value, 7200 or something. I thought that was simply the CNAME alias that would cache rather than the underlying IP/A Record, I just changed it to 5mins, hopefully this will help. Thanks. – Joe S Jun 14 '12 at 17:40

Your Answer


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

Browse other questions tagged or ask your own question.