Reply

MX records are present in the DNS UI but MX queries are failing.

New Poster
Posts: 1
Registered: ‎09-03-2018

MX records are present in the DNS UI but MX queries are failing.

by StaceyRichards New Poster
Message 1 of 1 (419 Views)

In My Vodafone for out domain, there are six MX records pointing to Google mail servers. This has been the case for many years.

 

Today we started to find that some people weren't able to send us email; their MX lookups for our domain were failing.

 

I have used nslookup to find out what's going on.

 

First I queried for the NS records:

 

>nslookup -q=NS mydomain.com
Server: UnKnown
Address: fe80::1

Non-authoritative answer:
mydomain.com nameserver = ns1.ihug.net.nz
mydomain.com nameserver = ns2.ihug.net.nz

 

Then I queried those name servers for the MX records:

 

>nslookup -q=MX mydomain.com ns1.ihug.net.nz
Server: ns1.vf.net.nz
Address: 203.109.134.2

mydomain.com
primary name server = ns1.vodafone.co.nz
responsible mail addr = hostmaster.mydomain.com
serial = 2018030703
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 7200 (2 hours)

 

Does this mean that Vodafone's name server is not replying with the MX records that have been set in My Vodafone for the domain?

 

I tried Google's name server:

 

>nslookup -q=MX mydomain.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
mydomain.com MX preference = 20, mail exchanger = alt1.aspmx.l.google.com
mydomain.com MX preference = 30, mail exchanger = aspmx3.googlemail.com
mydomain.com MX preference = 30, mail exchanger = aspmx4.googlemail.com
mydomain.com MX preference = 20, mail exchanger = alt2.aspmx.l.google.com
mydomain.com MX preference = 30, mail exchanger = aspmx2.googlemail.com
mydomain.com MX preference = 10, mail exchanger = aspmx.l.google.com

 

That seems to give a better reply. If I query Google's name server many times, I sometimes get the same reply as I get from Vodafone's name server:

 

>nslookup -q=MX mydomain.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

mydomain.com
primary name server = ns1.vodafone.co.nz
responsible mail addr = hostmaster.mydomain.com
serial = 2018030703
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 7200 (2 hours)

 

It looks like some of Google's load-balanced name servers have the old, correct data and others have refreshed from Vodafone with bad, non-existant data.

 

Has anyone else come across this before or know how to fix it.

 

I have duplicated the DNS records to a different DNS provider but am waiting for Vodafone to respond to my request for them to change the authoritative name servers for our domain to the different provider.

 

I'm now finding that our A, TXT and CNAME records are failing in the same way.

 

Any help would be much appreciated.

Stats
  • 0 Replies
  • 28w ago
  • 420 Views
  • 0 Kudos
  • 1 Contributor