Hi,

2 weeks ago I moved 3 websites from one host to another, I did so by transferring the sites and having the glue on the nameservers updated.

All fine until a couple of days ago. Suddenly the client, when entering one of her domain names, got an "account suspended" message. This was becuase I'd suspended the account on the old server. Then when I checked, I could access all the sites correctly but when I pinged one of the nameservers, it returned the old IP Address.

The next morning all seemed well, but one of the clients visitors tried to visit the site today and got the account suspended message again - does anyone have any idea of whats going on?

Thanks

Zones updated or glue not updated/propagated to all registries?

Helpful to post at least one domain to test thoroughly.

You updated the glue records, but did you update the definitions in the native registry, too?

Hi,

I didnt do the change personally, my domain registraar did - I rang them to check and they confirmed all seemed ok.

Sample domain is :

http://www.northern-pleasures.com

Any assistance gratefully received :-)

ns3/4.electrahosting.com glue isn't updated, and they don't have A records for themselves either.

Seems like your nameservers are unreachable at all at a time of writing:

http://private.dnsstuff.com/tools/dnsreport.ch?domain=northern-pleasures.com&token=2210e4d29ac2ac063f129e8536294019

A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding.

Are these issues caused by the domain company not updating things correctly at their end, or is it a configuration issue with my hosting company?


According to my host they are having to rebuild Named at the moment, is this related?

Which are the new/proper IPs? 195.x.x.x or 80.x.x.x?

The 80.* don't answer now, the 195.* do, so I think they're the likely ones... the 80.* are still in glue, and in the additional I get from the 195... and other problems.

The 195* address is the old one.

The 80* address is the new one.

The 80* one has been down for 2 hours now due to an issue with the named service that apparantly requires a rebuild but I have no further updates on that.

I could do with tracking down where the problem is - ie with the domain company not updating the nameservers properly or with the hosts not configuring something on their server properly?

Glue is right then. Good.

Then the rest is hard to tell until named is working at the end servers.

You also need to have the IPs updated in the ns1/ns2.electrahosting.com then. That answer is strange, and also wrong - someone missed a period (never a good thing ;-P )

;; ANSWER SECTION:
ns3.electrahosting.com. 120 IN A 195.242.213.36

;; AUTHORITY SECTION:
electrahosting.com. 120 IN NS ns1.electrahosting.com.electrahosting.com.
electrahosting.com. 120 IN NS ns2.electrahosting.com.electrahosting.com.

ns1.electrahosting.com and ns2.electrahosting.com point to a different server and are working correctly.

I'll repost once named is working (how long should that take? Its been 2 and a half hours now) and then hopefully we can get to the bottom of it - thanks for all your help!

Yes, they are different servers, but you shouldn't rely solely on the glue records - ns1 and ns2 should be giving out the proper A records (and those additional NS records are messed as well) for ns3/ns4 regardless. That should be fixed at least.

The rest we can see when the nameservers themselves are working.

Ok the server is working again now so hopefully we can get to the bottom of this.

So basically there needs to be a change for ns1 & ns2 in relation to ns3 & ns4 - where is this done, with the domain name company into the central registry or is this done on the server where ns1 and ns2 point to?

I found the offending A records at ns1/ns2 for the ns3/ns4 and changed them this morning, hopefully that will make things look a lot better! :)

Looks better, yes.

Still likely missing a period, or the NS records are made up wrong on ns1/ns2:

electrahosting.com. 120 IN NS ns1.electrahosting.com.electrahosting.com.
electrahosting.com. 120 IN NS ns2.electrahosting.com.electrahosting.com.

Looks better, yes.

Still likely missing a period, or the NS records are made up wrong on ns1/ns2:

electrahosting.com. 120 IN NS ns1.electrahosting.com.electrahosting.com.
electrahosting.com. 120 IN NS ns2.electrahosting.com.electrahosting.com.

Yeah, as lamerfreak says, you are missing some dots are you can just put "ns1" and "ns2"... You no not need "ns1.electrahosting.com"
So you can use "ns1" or "ns1.electrahosting.com.".... but "ns1.electrahosting.com" will give you the problem you see above.

But also.... why would you ever put a TTL of 120 seconds on your NS records.... You change name servers every 120 seconds?

This is what the control panel shows when i log in :

electrahosting.com. A 195.242.213.200
ftp A 195.242.213.200
localhost A 127.0.0.1
mail A 195.242.213.200
ns1 A 195.242.213.201
ns2 A 195.242.213.202
ns3.electrahosting.com. A 80.76.219.98
ns4.electrahosting.com. A 80.76.219.99
ns5.electrahosting.com. A 83.142.25.75
ns6.electrahosting.com. A 83.142.25.76
pop A 195.242.213.200
www A 195.242.213.200
electrahosting.com. NS ns1.electrahosting.com
electrahosting.com. NS ns2.electrahosting.com
mail MX 10
electrahosting.com. TXT "v=spf1 a mx ip4:195.242.213.200 ~all"

Which ones need amending?

electrahosting.com. NS ns1.electrahosting.com
electrahosting.com. NS ns2.electrahosting.com


Should be:
electrahosting.com. NS ns1.electrahosting.com.
electrahosting.com. NS ns2.electrahosting.com.

Where can you set your TTLs?