Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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've changed nameserver records for my domain name, migrating the dns to AWS Route53. I've updated the dns a week ago, changing the value for the cname record "mail.". I can see it working fine while other members of the team still see the old destination. The current TTL is 3600 (don't know what it was before to change nameserver), but I can't really figure out how can I force them to see the new destination (now it's a week I set the new record). It seems they are still quering the old namespace, or the cache dns server they are hitting is not up to date with the changes...

What do you suggest to handle this situation? It may afflict also other visitors for our website.

This is the output I get running dig +trace +norec a

; <<>> DiG 9.8.1-P1 <<>> +trace +norec a
;; global options: +cmd
.           3600    IN  NS  FWDR-58.FWDR-0.FWDR-253.FWDR-207.
.           3600    IN  NS  FWDR-62.FWDR-0.FWDR-253.FWDR-207.
.           3600    IN  NS  FWDR-41.FWDR-17.FWDR-37.FWDR-85.
.           3600    IN  NS  FWDR-83.FWDR-28.FWDR-38.FWDR-85.
;; Received 354 bytes from in 112 ms       4870    IN  NS       4870    IN  NS       4870    IN  NS       4870    IN  NS
;; Received 235 bytes from in 348 ms      300 IN  CNAME
;; Received 59 bytes from in 66 ms
share|improve this question
It's not my fault if none of the answers for my prev questions were not working. btw I accepted 1 answer that has received more votes on a suggestion I asked for. – CodeShining Sep 13 '12 at 12:29
Please provide some output from dig commands like "dig +trace +norec a" using your domain name instead of (replace your domain name back to in the output if you need to keep your domain unexposed). – Skaperen Sep 13 '12 at 12:29
@Skaperen Hi, thanks for the interest. I added the output from the command you suggested to the question above. – CodeShining Sep 13 '12 at 12:36
Regarding your accept rate @AnsgarWiechers is right, its pretty low, not horrible. There were multiple legit answers to a couple of your questions, not to mention one of them was a complete duplicate of another question. Oh, and if none of those suggestions helped you should really post comments against them until the issue is resolved or post your own answer tell everyone how YOU fixed it. Its bad form to leave questions open like that, doesn't help the next guy searching on Google. – Brent Pabst Sep 13 '12 at 12:44
The DNS looks OK so far. At this point more needs to be explored, both from your perspective and other people's perspective. We may need to know the actual domain for this case. Or you may need to get someone on-site. – Skaperen Sep 14 '12 at 2:55
up vote 0 down vote accepted

I found that people seeing the old webserver was caused by a record they specified directly inside /etc/hosts, where they declared the IP resolution. So querying the record they were not able to reach the DNS.

By removing that lines and flushing the local dns cache all went right.

Hope this helps someone else having the same issue.

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.