gregmcc
Honorary Master
Looks like the wrong record is on ns.otherdns.net
Is this server still on the registrar?
Is this server still on the registrar?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Google Maps vs Waze vs Apple Maps vs physical paper maps?
MX change not propagating
- Thread starter ld13
- Start date
Sinbad
Honorary Master
- Joined
- Jun 5, 2006
- Messages
- 88,590
- Reaction score
- 41,091
Name Server: ns.dns1.co.za
Name Server: ns.dns2.co.za
Name Server: ns.otherdns.net
Name Server: ns.otherdns.com
But when I query otherdns.net I get the right result
ld13
Honorary Master
No bulk emails here, but yeah I'm still setting up all the fancy stuff. I'm just sitting here puzzling over what started as a stray mimceast email that landed in an old inbox. At first I thought I'd forgotten to remove the old MX record—nope, I had. Then I thought maybe I'd remembered my MX priorities wrong—nope, those were fine too.
ld13
Honorary Master
still with Afrihost yes
gregmcc
Honorary Master
Yeah, this one is poked. Constantly giving me the bad record.
Sinbad
Honorary Master
- Joined
- Jun 5, 2006
- Messages
- 88,590
- Reaction score
- 41,091
There are two IPs for that name
154.0.6.120 returns the wrong info
149.28.240.39 returns the correct records.
Otherdns need to fix their server.
Short term fix if you can, remove it as an NS from your zone and registrar.
ld13
Honorary Master
Bingo, getting the incorrect MX from the second ip. @Afrigirl wtf??
ns.otherdns.net has been taken outside and shot
Code:
; <<>> DiG 9.17.12 <<>> [removed].co.za MX @154.0.6.120 +cmd +stats +question +answer +authority +additional +edns=0 +rd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45450
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;[removed].co.za. IN MX
;; ANSWER SECTION:
[removed].co.za. 14401 IN MX 10 mx1600899.spe.ucebox.co.za.
;; Query time: 23 msec
;; SERVER: 154.0.6.120#53(154.0.6.120) (UDP)
;; WHEN: Wed Jan 07 21:44:10 South Africa Standard Time 2026
;; MSG SIZE rcvd: 79
C:\Users\x>"C:\Users\x\AppData\Local\Microsoft\WinGet\Packages\ISC.Bind_Microsoft.Winget.Source_8wekyb3d8bbwe\dig.exe" [removed].co.za MX @149.28.240.39 +cmd +stats +question +answer +authority +additional +edns=0 +rd
; <<>> DiG 9.17.12 <<>> [removed].co.za MX @149.28.240.39 +cmd +stats +question +answer +authority +additional +edns=0 +rd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61477
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;[removed].co.za. IN MX
;; ANSWER SECTION:
[removed].co.za. 1000 IN MX 9 SMTP.GOOGLE.COM.
;; Query time: 303 msec
;; SERVER: 149.28.240.39#53(149.28.240.39) (UDP)
;; WHEN: Wed Jan 07 21:45:02 South Africa Standard Time 2026
;; MSG SIZE rcvd: 73
Last edited:
ld13
Honorary Master
Now how do I explain to the higher ups that this was a server issue and not something we had control over?
Last edited:
Sinbad
Honorary Master
- Joined
- Jun 5, 2006
- Messages
- 88,590
- Reaction score
- 41,091
Simple. Just show the two different results from the two Otherdns servers and explain that one of them is broken and it's not run by you... And that it was poisoning the lookups. As soon you identified that you removed it from the pool of servers and the problem was resolved.
gregmcc
Honorary Master
Easy enough to show and proof.
The incorrect records are coming from a authoritive name server outside of your control.
You can:
a) Remove it
b) Try update the record which will trigger a replication and maybe fix it on the broken server (Though I wouldn't hold my breath on this. The 2 otherdns servers have replicated and have the same serial number so there is something horribly broken with it's cache. Though if you update it to a temp record and then back to the correct record there will be a outtage - so scrap this idea
c) Wait for AH to fix it.
The incorrect records are coming from a authoritive name server outside of your control.
You can:
a) Remove it
b) Try update the record which will trigger a replication and maybe fix it on the broken server (Though I wouldn't hold my breath on this. The 2 otherdns servers have replicated and have the same serial number so there is something horribly broken with it's cache. Though if you update it to a temp record and then back to the correct record there will be a outtage - so scrap this idea
c) Wait for AH to fix it.
ld13
Honorary Master
Already removed the offending DNS server and tweaked the TTL.
To state the question better: How do I explain to a non-technical person that this was due to a borked server
Sinbad
Honorary Master
- Joined
- Jun 5, 2006
- Messages
- 88,590
- Reaction score
- 41,091
Our dns was handled by 4 of afrihost's nameservers that should automatically sync themselves with updates made to the configuration.
One of the servers did not sync properly and so was returning old data. We have raised the issue with afrihost and also temporarily taken that server out of our setup.
