Hello,
I have the same problem: "Status: Pending" and Prefix with "No auth on file"

I send loa through e-mail like ipv6@he.net for review
But I didn't get any reply.

How log does it normaly take to setup BGP after sending the LOA and can I check if something is wrong with my IRR?

Thanks

Retried on both my /64 and /48 (allocated by HE.net).

Reset to explorer, made it back to Administrator without any issues...so mail transfer is working...

Still getting "unable to find MX for domain," which is odd, because my postfix server is receiving emails from he.net without any issues.

Whatever it is, it's failing quickly. I guess we'll wait and see on our respective support tickets...

I'm in the middle of moving one of my DNS zones from another provider onto dns.he.net.

However, it looks like the old NS and SOA records have quite a long TTL (1 day), and I can't do anything to decrease the TTL at the old provider.

These records seem to have been cached by HE.  So now, despite the authoritative servers for the TLD serving the new delegation, I'm still unable to get HE to serve the zone, which means my site is down.

It'd be really really nice if there was a way to ask HE to ignore its cache of such records when re-checking delegation, to avoid this scenario.

Isn’t the test to see if you can run a mail server?  Therefore, it probably has to be in your netblock.

Hmmmm... Actually, it's part of a different /64 (also a tunnelbroker.net one, but on a different account). I might install a small mail server on my own /64 and reset/redo the certification again to see if that fixes it.

I have logged a ticket with HE support, but no reply on that yet.

thekrugers, is your MX server part of your /48 or /64?

I'm just going to me-too this post. I am having the same exact issue - could this be at the application level?

ansible:~ # dig mx engyak.net +short
1 mx.engyak.net.
ansible:~ # dig aaaa mx.engyak.net +short
2001:470:e8a3:e060::100
ansible:~ # dig +short -x 2001:470:e8a3:e060::100

The domain is andykruger.co.za. I believe the checks done for the test are a mx, aaaa and -x dig, so I did some myself:

andy@ubuntu-srv:~$ dig mx andykruger.co.za +short
10 mail6.andykruger.co.za.
20 mail4.andykruger.co.za.
andy@ubuntu-srv:~$ dig aaaa mail6.andykruger.co.za +short
2001:470:1f23:fd:215:5dff:fe07:724
andy@ubuntu-srv:~$ dig -x 2001:470:1f23:fd:215:5dff:fe07:724 +short
mail6.andykruger.co.za.

I just tried the test again and it still says it can't find the MX for the domain. Since the domain doesn't carry any important email (it only has one address, the one I used for the Admin test), I've just deleted the MX RR referring to mail4, so now it only has an IPv6 MX server. I'll give it an hour or so and try the test button again.

Which domain?

I'm a bit confused as to how this is even possible. My Professional level test is stuck on an error message Unable to find MX for domain right after the Administrator level test found the MX for the domain and sent an email to the domain.

I've even reset and started the tests over with a lower level domain after being stuck with this problem for a couple of days, I was doing the cert on a subdomain and moved it up to the main domain.

Now sure, I would expect the Professional level test to fail with something like RDNS does not match or something similar for a couple of hours because the old PTR RR has a TTL of 24 hours, but to be stuck on Unable to find MX for domain right after the Administrator test managed to find the MX and send mail via it seems a bit strange.