Nameservers Still State Waiting on Update

It has been 3 days now since I updated the name servers for my domain.

My TTL on my NS records is set to 7200, so it should have been completed by now, yet my domain still shows that the nameserver update is needed.

Your nameservers still point to wmhost. You need to point them to Cloudflare, recheck them, and it should work eventually.

As I already stated, they were updated 3 days ago to the ones provided to me by Cloudflares panel
And as you can see here, I wasnt lying about that: Screenshot by Lightshot

The whois still shows your old nameservers. You will need to check with your registrar as to why your changes haven’t been propagated yet.

Edit: looks like you just changed NS records in the DNS config on the old nameservers. That’s not going to work. There needs to be another place where you can edit the nameservers.

1 Like

You aren’t lying, but you didn’t change the correct settings. You are adding NS records within your zone hosted on, this is not correct, instead you must change the nameserver records with your domain registrar.

1 Like

The domain is registered and Nameservers are provided by Amazon Route 53 services.

As I showed in the control panel screenshot, I assure they are updated properly. The only issue I can possibly see is the SOA record.

If you registered your domain with Route 53, you will need to follow this guide:

You can skip the part about glue records.

To activate a domain on Cloudflare you need to set the nameservers to Cloudflare and only Cloudflare.

Domain Name: GETYOU.ONL
Registry Domain ID: D2334074-AGRS
Registrar WHOIS Server:
**   Registrar URL:**
Updated Date: 2018-08-03T13:56:06Z
Creation Date: 2014-04-28T13:33:46Z
Registry Expiry Date: 2020-04-28T13:33:46Z
Registrar Registration Expiration Date:
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.170377661
Domain Status: clientTransferProhibited
Domain Status: serverTransferProhibited
Registrant Organization: Get You Online
Registrant State/Province: MA
Registrant Country: US
**    Name Server: NS1.WMHOST.CC**
**    Name Server: NS3.WMHOST.CC**
**    Name Server: NS2.WMHOST.CC**
**    Name Server: NS4.WMHOST.CC**
DNSSEC: unsigned

That isn’t where they are pointed. As @thedaveCA said, you’ve changed the wrong setting. This change must be made with your registrar in the registrar related settings for the zone.

1 Like

Looks at the 2nd screenshot please.

I am obviously wasting my time here, seems nobody can read, even CF Team.

I will take my domain, and service elsewhere.

1 Like

The whois shows the nameservers haven’t been changed as I posted. You can search and see this for yourself. ICANN Lookup Dig demonstrated that as well. I wish you the best of luck with whatever service you decide on, take care.

dig ns +trace

; <<>> DiG 9.11.1 <<>> ns +trace
;; global options: +cmd
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	NS
.			239043	IN	RRSIG	NS 8 0 518400 20180925050000 20180912040000 41656 . 094S8BUA/KAlFgCsEozaekZEMhLaYw4w0DADDnwwAmmaEYf5Y41jKjO/ rEahj0DuKPTmbXxddL1UyT23bEikLd8j0C+3koem2aEG9e1BBNXCQZet pFWWWbJNriZ4Lcx61DlV5vX72EGVWsP6DuUILm7cNqWncVIDDRq3xBee mR4FDAA6Ssc1EkEI3kq7oLv6uWNnoG1JziiPvgNNUB+1NQVgxw+UDBaB zu1pzJQiAMgXF1bOQpzxbYMzjPjBBj9DXvO+N9c5XVFYfYykyc89Wyio ImjCzqHyzr5AosUiDF16lXJiJrKdy+Ok2Ia9SOQtz8VOR4eNDWfTESF1 MsCZ8w==
;; Received 525 bytes from in 10 ms

onl.			172800	IN	NS
onl.			172800	IN	NS
onl.			172800	IN	NS
onl.			172800	IN	NS
onl.			86400	IN	DS	28830 7 1 43C8D1479E0457EAD6020024017FDEC8CCE2260D
onl.			86400	IN	DS	28830 7 2 18EB9FAA635692104783C62A7F6F51AA17365BB07689093A247183D3 9B88338D
onl.			86400	IN	RRSIG	DS 8 1 86400 20180926170000 20180913160000 41656 . YGmOYuAE+uwnKl1Gdl2hVRRPGzscTR5VxWtTlNaBOYlKTtylFy/XXwsn S8BxpIbVLQ47Vlw3OVq4KG0SazA0W9iDGgGP2Nqadh30PzD/lgC9XFkM QRQLTLgsFwRMun9NFwhogjMkloaHI9q3djWliK+BEeaGGIq7gWNLHmlZ zSQT74Y0FeDEYhLhia30r3XSwLZVhMRLMAHk+yqcQfvHj7Umq6QdHY/t pkvK+N51ZCIAXpujDLszHE8gaGvfSBkouyTqOtKh4sWQp/dES9s7+nSK zrSGJuj1SlX50t7K8Fgk5J6iVnX8aVWEMnFaYCdGoEZyrGkDaKNmhW9U zkTn+g==
;; Received 658 bytes from in 55 ms		3600	IN	NS		3600	IN	NS		3600	IN	NS		3600	IN	NS 900 IN NSEC3 1 1 1 D399EAAB OJMT71EKDGUNEO6AQAG6F51MN7L1ONMK  NS SOA RRSIG DNSKEY NSEC3PARAM 900 IN RRSIG NSEC3 7 2 900 20181004191859 20180913181859 23649 onl. cm3XKOyl4MSqjD9C79zEpFwc3x1YEFTa7PVQkhKXhYsOMRlhzX9oK9wQ 0mt5oioB5s1QFPxWN3BUSw2640AbPphbX5j0ETOHyxXYaC1VIcadFJM9 cRujdMgCubZYWk2unbYzeayTQuCGLOIK0RBzcnPw+DqcUm2vRvPH1rTV 7Hk= 900 IN NSEC3 1 1 1 D399EAAB 5R8TSS5P021VJOHPDVBLE6L366SGT59C 900 IN RRSIG NSEC3 7 2 900 20180930154546 20180909144546 23649 onl. L/s91mOBB0BiIoxUTqKQtzJSacWNVT7ZowaRhVgwn5Ocg39wOzFwYOqf L7V++BeXtg3cIqu+fxCEFaDEyqE/I5yLT5hddh9e6CdroZTJATJ8bYtQ w7F1JuFOVRYKSR51K/KyKVrp6hO9gOhnc9t4k3AteZTjCDSeMyluPkC/ r0U=
;; Received 605 bytes from in 36 ms		7200	IN	NS		7200	IN	NS
;; Received 94 bytes from in 40 ms
1 Like

You cannot use Route53 and CF at the same time for domain root DNS zone.

There is no reason in becoming snippy. As I - and many others meanwhile - have told you nine hours ago you have changed your nameservers, but in the wrong place. As long as you dont fix this it wont work, regardless of where you take your domain.


And it is not Amazon where you need to change anything, but Gandi, the registrar of that domain. If Amazon registered it on your behalf at Gandi, it might be that you need to change it within Amazon (I dont know how their connection is) but the change has to reach Gandi eventually and subsequently the registry.