DNS Propagation - severe delay

I can't find a more appropriate forum for this question so here goes.

I made changes to the MX records for a domain on 17th August 2020. A month later there are still DNS servers throughout the world that are showing the old MX records, see https://dnschecker.org/#MX/lighthouseprojectcrawley.org

Anything showing 0:lighthouseprojectcrawley.org has still not caught up with the change, which was done when the domain was converted to use G Suite. I am used to changes taking a day or two to propagate but this is ridiculous. The TTL value on the records is 3600. Is there anything I can do to resolve this?

Thanks

You have two nameservers set up for this domain, ns1.365hosts.network and ns2.365hosts.network

The problem is, they disagree on what the mx record is:

C:\>dig @ns1.365hosts.network lighthouseprojectcrawley.org mx

; <<>> DiG 9.16.5 <<>> @ns1.365hosts.network lighthouseprojectcrawley.org mx
; (5 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12760
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1680
;; QUESTION SECTION:
;lighthouseprojectcrawley.org.  IN      MX

;; ANSWER SECTION:
lighthouseprojectcrawley.org. 14400 IN  MX      0 lighthouseprojectcrawley.org.

;; ADDITIONAL SECTION:
lighthouseprojectcrawley.org. 14400 IN  A       154.16.202.155

;; Query time: 11 msec
;; SERVER: 179.61.204.11#53(179.61.204.11)
;; WHEN: Thu Sep 17 20:13:21 GMT Summer Time 2020
;; MSG SIZE  rcvd: 89

C:\>dig @ns2.365hosts.network lighthouseprojectcrawley.org mx

; <<>> DiG 9.16.5 <<>> @ns2.365hosts.network lighthouseprojectcrawley.org mx
; (4 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29055
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1680
;; QUESTION SECTION:
;lighthouseprojectcrawley.org.  IN      MX

;; ANSWER SECTION:
lighthouseprojectcrawley.org. 3600 IN   MX      10 alt4.aspmx.l.google.com.
lighthouseprojectcrawley.org. 3600 IN   MX      5 alt1.aspmx.l.google.com.
lighthouseprojectcrawley.org. 3600 IN   MX      5 alt2.aspmx.l.google.com.
lighthouseprojectcrawley.org. 3600 IN   MX      10 alt3.aspmx.l.google.com.
lighthouseprojectcrawley.org. 3600 IN   MX      1 aspmx.l.google.com.

;; Query time: 15 msec
;; SERVER: 5.252.161.168#53(5.252.161.168)
;; WHEN: Thu Sep 17 20:13:23 GMT Summer Time 2020
;; MSG SIZE  rcvd: 175

In reply to a post by Oliver341:

You have two nameservers set up for this domain, ns1.365hosts.network and ns2.365hosts.network

The problem is, they disagree on what the mx record is:

Wow, thank you, so simple, why did I not think to check that. Now I've just got to work out why cPanel is only updating one of the name servers.

Each of those two nameservers resolves to several IP addresses. If just one of those IP addresses returns the wrong dns record, you will have problems. Possibly some of these IP addresses associated with the nameservers are stale and should not be there.

; <<>> DiG 9.16.5 <<>> ns1.365hosts.network
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23800
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 2, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns1.365hosts.network.          IN      A

;; ANSWER SECTION:
ns1.365hosts.network.   60      IN      A       179.61.204.2
ns1.365hosts.network.   1799    IN      A       109.203.110.15
ns1.365hosts.network.   60      IN      A       179.61.204.11
ns1.365hosts.network.   1799    IN      A       5.77.60.198
ns1.365hosts.network.   60      IN      A       5.252.161.112

;; AUTHORITY SECTION:
365hosts.network.       595     IN      NS      pdns1.registrar-servers.com.
365hosts.network.       595     IN      NS      pdns2.registrar-servers.com.

;; Query time: 35 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Thu Sep 17 20:37:50 GMT Summer Time 2020
;; MSG SIZE  rcvd: 190

; <<>> DiG 9.16.5 <<>> ns2.365hosts.network
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 2, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns2.365hosts.network.          IN      A

;; ANSWER SECTION:
ns2.365hosts.network.   60      IN      A       179.61.204.9
ns2.365hosts.network.   1799    IN      A       5.77.60.198
ns2.365hosts.network.   1799    IN      A       109.203.110.15
ns2.365hosts.network.   60      IN      A       5.252.161.168

;; AUTHORITY SECTION:
365hosts.network.       1112    IN      NS      pdns1.registrar-servers.com.
365hosts.network.       1112    IN      NS      pdns2.registrar-servers.com.

;; Query time: 31 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Thu Sep 17 20:38:06 GMT Summer Time 2020
;; MSG SIZE  rcvd: 174

In reply to a post by Oliver341:

Each of those two nameservers resolves to several IP addresses. If just one of those IP addresses returns the wrong dns record, you will have problems. Possibly some of these IP addresses associated with the nameservers are stale and should not be there.

Does that then mean that either of the name servers could sometimes be returning the wrong result?

In reply to a post by kasg:

Does that then mean that either of the name servers could sometimes be returning the wrong result?

Yup. It all depends on what IP address the nameserver resolves to at any one time.

Right, I think I'm going to redelegate the name servers somewhere else (1-2-3, with whom the domain is registered) and set up the entries there as I don't think I trust 365 Hosts to sort this out. Thanks very much for your help, Oliver.

No problem. 👍

All done now. Strangely whatsmydns.net reports that it has all propagated (well almost, Sprint hasn't got the name server change) but dnschecker.org lags behind.

https://www.whatsmydns.net/#NS/lighthouseprojectcraw...
https://www.whatsmydns.net/#MX/lighthouseprojectcraw...
https://dnschecker.org/#NS/lighthouseprojectcrawley.org
https://dnschecker.org/#MX/lighthouseprojectcrawley.org

Edited by kasg (Fri 18-Sep-20 21:37:54)

Fixed! Now it's just a short matter of time.