-3

After changing name servers of recently acquired domain, I receive this SERVFAIL error running dig on the domain name. GoDaddy, where I buy domain name, says it's not their fault because the WHOIS records update. Company where I point domain (Amazon) also take no responsibility.

->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 

This is my question: Is SERVFAIL error related to changing of name servers? (i.e. could this be a Godaddy cause problem did not change name servers correctly), or is SERVFAIL error only come from company where name servers now point, and it only coincidence that happen at time when change name servers?

  • any reason not to tell us exact domain name? – Dusan Bajic Aug 28 '14 at 12:24
  • @dusan.bajic people can obtain personal information through domain name i think (which can be unsafe) but if there is certain information you require from domain name to solve problem please tell me and i update the post with new information – Tomoko Yamaguchi Aug 28 '14 at 12:26
  • When did you change name servers? – Dusan Bajic Aug 28 '14 at 12:36
  • @dusan.bajic name servers changed yesterday. WHOIS records show name servers have been changed – Tomoko Yamaguchi Aug 28 '14 at 12:45
  • Do you get correct results if you run DIG with +trace option? – Dusan Bajic Aug 28 '14 at 12:58
  • I don't know what "correct" results would be for +trace option, but this is what I get (please note the `xxx` is for the home router ip address). Is this what you expect? `;; global options: +cmd ;; Received 12 bytes from 1XX.1XXX.0.1#53(1XX.1XX.0.1) in 310 ms` – Tomoko Yamaguchi Aug 28 '14 at 13:20
  • @dusan.bajic I'm have trouble signing into chat, but I saw your comment about expecting to see IP address. I'm not sure what I expected to see from +trace – Tomoko Yamaguchi Aug 28 '14 at 13:41
  • @dusan.bajic I don't have enough reputation to go into chat. Need 20 points. – Tomoko Yamaguchi Aug 28 '14 at 13:41
  • http://chat.stackoverflow.com/rooms/info/60174/servfail?tab=general – Dusan Bajic Aug 28 '14 at 13:52
  • Without the domain name there is noting we can really do to help – user9517 Aug 28 '14 at 20:40
  • @Iain sorry, i disagree. You (or someone who cares to answer) can tell me steps to follow. But thank you if you do not wish – Tomoko Yamaguchi Aug 29 '14 at 16:22
  • Please read http://meta.serverfault.com/questions/963/what-information-should-i-include-or-obfuscate-in-my-posts especially the NB under _Host names and domain names_. – user9517 Aug 29 '14 at 16:32
  • @Iain thank you. I read but in absence of domain name steps can be provided to follow. Change name servers is very common, steps to follow if no work probably also very common. – Tomoko Yamaguchi Aug 29 '14 at 17:27
  • It really is much more instructive for the clueless if you can work with their data. I was just trying to help you get your problem solved. As it is it will likely be closed before that happens - your problem not mine. – user9517 Aug 29 '14 at 17:34
  • @Iain I am sorry I make you angry. "Your problem not mine" that is an angry statement, yes? – Tomoko Yamaguchi Aug 29 '14 at 20:35

1 Answers1

1

If the workstation where you run the dig command is using google public DNS (8.8.8.8), they recently implemented DNSSEC validation. They return SERVFAIL for domains that fail this validation. Maybe the domain needs DNSSEC?

wrk2bike
  • 56
  • 3