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 recently transferred one of my domains to a new server, and ever since I am having intermittent issues accessing the site. does not work, occasionally works, and email also does not work.

Despite trying a couple of DNS testing utils online, it appears that the domain is not resolving to the server correctly.

A Whois check shows the following nameservers:

Primary Name Server Hostname: NS1.GAVINCOATES.COM
Secondary Name Server Hostname: NS2.GAVINCOATES.COM

The domain is configured on the same server, and this website resolves fine.

The domain is configured as follows with the registrar ( domain settings

Within plesk on the server, the configuration for is as follows: hosting settings in plesk

The hosting settings in Plesk for domain is as follows:

enter image description here

Thanks in advance.

share|improve this question
did you change the name servers for the domain too? – Alnitak Dec 19 '11 at 15:36

First, check the .com servers:

% dig ns
;; AUTHORITY SECTION:   172800  IN  NS   172800  IN  NS
;; ADDITIONAL SECTION:    172800  IN  A    172800  IN  A

These appear to be the old server addresses?

Let's also check

% dig ns
;; ANSWER SECTION:   86400   IN  NS

Uh oh, we have a mismatch. Your records at the .com registry are inconsistent both in name and in the glue records.

You need to have your domain updated with your registrar to use the right name ( ) and because the NS is in its own zone you'll need to send them the right IP address for its glue record too.

share|improve this answer
I have changed the NS record in plesk for from NS to NS1, and the website now appears to load correctly. However, doing dig ns still shows the old IP addresses. Why is this, and what is a glue record? The only setting for the domain with the registrar, is to use ns1/ as the name server. – Gavin Coates Dec 19 '11 at 16:15
@GavinCoates you should talk to your registrar - they should be able to advise how to change the parent zone's NS records and add the glue record. – Alnitak Dec 19 '11 at 16:16
@GavinCoates p.s. despite what you've written above, according to Verisign the name servers for are ns[01] - they are not pointing at your own server. – Alnitak Dec 19 '11 at 16:25 nameserver is not set, instead I have created a series of A records that point to the correct server IP - see image 1 in my original post. Is this not correct? – Gavin Coates Dec 19 '11 at 16:38
@GavinCoates it has to be set both in the parent zone and in the zone itself, and the two should be consistent. – Alnitak Dec 19 '11 at 16:39

One issue is that delegation to is set to and however querying the zone returns only

A second issue is that both and resolve to the same address. This is the same address that resolves to.

$ host has address
$ host has address

I have performed a dig against your DNS server and it seems to respond with the records correctly:

; <<>> DiG 9.5.0-P2 <<>> any
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1716
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;              IN      ANY

;; ANSWER SECTION:       86400   IN      MX      20       86400   IN      MX      20       86400   IN      MX      30       86400   IN      MX      30       86400   IN      MX      30       86400   IN      MX      30       86400   IN      MX      10       86400   IN      SOA 1323190098 10800 3600 604800 10800       86400   IN      NS       86400   IN      A

;; ADDITIONAL SECTION:    86400   IN      A

;; Query time: 36 msec
;; WHEN: Mon Dec 19 15:21:40 2011
;; MSG SIZE  rcvd: 315

Did you leave enough propagation time after changing server before running your tests?

share|improve this answer
I have left it for about 4 days to allow any changes to fully propogate. What exactly do you mean by ` querying the zone returns only` - and how do i go about changing this? – Gavin Coates Dec 19 '11 at 15:35
See Alnitak's answer above. You need to fix your zone file as well as your glue records. – James O'Gorman Dec 19 '11 at 17:05

Looks like your Nameservers are not responding correctly.

Not the items in red. These will typically result in odd DNS behavor.

Appears your nameservers are not returning NS records for your domain. You need to have NS records for your domain.

share|improve this answer
why are my ns1/ns2 showing the old server IP addresses? I guess this is what is causing problems, yet everything on the domain is configured to use the new IP addresses?? – Gavin Coates Dec 20 '11 at 10:31

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.