In message <20030917002145.71549.qmail(a)web13607.mail.yahoo.com>om>, Stephen Sheehan
Does anybody have a workaround. for .nz MX records
ewen@basilica:~ $ host -t MX eaudio.co.nz
eaudio.co.nz mail is handled by 10 mail.2day.com
ewen@basilica:~ $ host mail.2day.com
has address 220.127.116.11
The message you're seeing from 18.104.22.168 -- Verisign's wonderful
"all domains are ours" IP address -- is that it won't accept mail for
the domain eaudio.co.nz. No great surprise. It won't accept mail
for anything else either. In fact, it's got a very fixed pattern of
responses to absolutely anything at all you send it.
I suspect the MX record is cached, and the A record for mail.2day.com
isn't cached/available any longer.
If it weren't for Verisign adding their brokenness to the .com/.net DNS
yesterday, then you'd at least get a NXDOMAIN error on mail.2day.com
it'd be more obvious what was wrong.
If you want a work around I suggest something like the bind forward
entry that has already been posted on nznog, at some point where it's
visible to your mail server.
might be able to achieve some improvements by changing all
the MX records on the domains for which they handle DNS and Mail to
something not under 2day.com
and/or by doing a bulk update on the NZ
Register for the names that they host the DNS to nameservers not under
(but that'd need to be done carefully, and would have to wait
for zone push/cache expiry anyway).