Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Recently, I've been experiencing some downtime for my website www.nexttwist.com.

The downtime is intermittent and it may be up at one location while it is down in another physical location. For some users, when they change the DNS to 8.8.8.8 in their system, they've reported that it came back.

I then had a look into my DNS settings at http://www.intodns.com/nexttwist.com and found the errors (attached image):

enter image description here

I don't know if the error as shown is responsible for the downtime but can anyone explain me how to fix these errors?

share|improve this question
    
How you fix it depends on how it's supposed to work. Who is supposed to be providing name service for your domain and what nameservers did they tell you to use? –  David Schwartz May 22 '12 at 13:50
    
I'm hosting my application at AWS. There are no NS records in my DNS settings, I've an A record pointing to the host. –  ptamzz May 22 '12 at 13:54

1 Answer 1

up vote 3 down vote accepted

It looks like there's an inconsistency between what your registrar has in their database and what they pushed into the .com TLD database. If you didn't change it recently (in the past two hours or so), I'd talk to your registrar.

Domainmonster.com says:

Nameserver:             ns1.domainmonster.com
Nameserver:             ns2.domainmonster.com
Nameserver:             ns3.domainmonster.com

But the .com servers say:

nexttwist.com   nameserver = ns1.domainmonster.com.
nexttwist.com   nameserver = ns2.domainmonster.com.
nexttwist.com   nameserver = ns3.domainmonster.com.
nexttwist.com   nameserver = dns3.registrar-servers.com.
share|improve this answer
    
Thanks, I'll check with the registrar then. Just for my clarity, these two must be the same, right? (Pardon my ignorance) –  ptamzz May 22 '12 at 14:06
2  
They don't absolutely have to be the same. But the problem in this case is that dns3.registrar-servers.com is not actually providing any name service for your domain, and the .com master servers are directing people to it. This can cause their nameservers to time out. –  David Schwartz May 22 '12 at 14:07

Your Answer

 
discard

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.