Administrator Email Test

[yakatz]

For my IPv6 capable email address, I put .
The test returns: No MX found for your domain. Failed to get AAAA.
I found several references to this problem, but non that has been relevant to me.
I can not add MX records to the primary domain (well, I have access to add them, but no server set up to accept that mail).
Any thoughts?


(Email image from http://services.nexodyne.com/email/)

[cholzhauer]

I can not add MX records to the primary domain (well, I have access to add them, but no server set up to accept that mail).

I'm not sure I follow.  If you don't have access to create AAAA and MX records, you can't do any of the tests.

The domain you provided doesn't even have an A record, much less a MX or AAAA

[yakatz]

I'm not sure I follow.  If you don't have access to create AAAA and MX records, you can't do any of the tests.

The domain you provided doesn't even have an A record, much less a MX or AAAA

I said that I can create the records, but I don't want to add an MX record for @ because it messes up my Google Apps setup.
The host certainly does have A, MX and AAAA records:

C:\>nslookup
Default Server:  pfSense.home
Address:  192.168.200.1

> set type=ANY
> ym-linode-01.10815.net
Server:  pfSense.home
Address:  192.168.200.1

Non-authoritative answer:
ym-linode-01.10815.net  AAAA IPv6 address = 2600:3c03::f03c:91ff:fe93:fcc6
ym-linode-01.10815.net  MX preference = 10, mail exchanger = ym-linode-01.10815.net
ym-linode-01.10815.net  internet address = 173.255.228.160

ym-linode-01.10815.net  internet address = 173.255.228.160
ym-linode-01.10815.net  AAAA IPv6 address = 2600:3c03::f03c:91ff:fe93:fcc6
>

[cholzhauer]

Guess you're right...I must have mis-typed something earlier...my apologies

If you don't want to break your current setup, the only thing I can suggest to to create a sub-domain for testing

[yakatz]

If you don't want to break your current setup, the only thing I can suggest to to create a sub-domain for testing

That IS the subdomain. I was saying that I do not want to create records for 10815.net, but create them all at ym-linode-01.10815.net .

[jgeorge]

Your IP address for ym-linode-01.10815.net is odd to me. You show it as 2600:3c03::f03c:91ff:fe93:fcc6, abnd if I look it up from one server I get that reply, but looking it up from another location yields me 2001:470:1f07:a10::2. I *presume* that the 2001 address is the one you want (that's a HE tunnel) but if you have some DNS servers giving out different information, I'm pretty sure the test checks will fail if they come back and look for your setup at an IP address where it's not.

I can't ping you at either address, if that helps any.

Cheers,

Joe

[yakatz]

You show it as 2600:3c03::f03c:91ff:fe93:fcc6, abnd if I look it up from one server I get that reply, but looking it up from another location yields me 2001:470:1f07:a10::2.

Yes, I switch to Linode's native IPv6 as soon as it was available, but I switched back because Linode can not delegate DNS control yet (since they are not giving out real subnets yet, just internally routed addresses).
I suppose it could take up to 48 hours for the change to take effect everywhere, but I was having this problem before I switched the DNS.

I will wait another day and see what happens.
My suspicion is that the HE test does not want to send mail directly to the AAAA record, but only to the MX record.
My understanding is that if there is no MX record, it should try to route mail to the A/AAAA record.
Correct me if I am wrong...

[broquea]

We specifically look for MX records, rather than relying on it failing over to a/aaaa.

[yakatz]

We specifically look for MX records, rather than relying on it failing over to a/aaaa.

Any particular reason?
Maybe the page could say that...

[broquea]

Because in a modern internet, the majority of domains have a well defined MX record. We aren't using some SMTP client. We're checking DNS records for what handles mail and then a script connects directly.

I can not add MX records to the primary domain (well, I have access to add them, but no server set up to accept that mail).

If you have access to configure an IPv6 capable MTA (the point the test goes to prove), then you should use that dns access to create an MX.

Also, does this problem even exist anymore? Looks like there is an MX record to me, and ran this query on the machine we run the tests on:

Code Select Expand

;; ANSWER SECTION:
ym-linode-01.10815.net. 67075   IN      MX      10 ym-linode-01.10815.net.

;; ADDITIONAL SECTION:
ym-linode-01.10815.net. 67075   IN      AAAA    2600:3c03::f03c:91ff:fe93:fcc6


Ahh...I see, it just sits there never connecting:

Code Select Expand

~$ telnet 2600:3c03::f03c:91ff:fe93:fcc6 25
Trying 2600:3c03::f03c:91ff:fe93:fcc6...
^C


Should work after you've gotten email working...(dns change waiting to propagate I believe)

[yakatz]

As you may be able to see from my signature, I got it to work and I am now on to the next test.
My original issue seems to be a slow DNS update issue, the issue with it hanging was a stuck lockfile on my server.
It seems to me that there is some very slow DNS cache between the DNS server and the test server, since it can not find my rDNS for my MX either.
I am using the HE free DNS (I just switched from the Linode DNS earlier today).

[jgeorge]

Congrats!