Print

[DOMBlogger]

I set up rdns with my hosting company for my mail servers MX record a few hours ago.
The test still is not working, which I'm guessing means it just has not propagated yet.

Code: [Select]

[user@host ~] dig +short mail.domblogger.net AAAA
2600:3c00::f03c:91ff:fe93:ee82
[user@host ~] dig -x 2600:3c00::f03c:91ff:fe93:ee82 +short
mail.domblogger.net.

Since that is the MX listed domain, I assume that means it *will* work once the DNS properly propagates?

[cholzhauer]

It looks good on my end...how long ago did you make the change?  Give it a day and if it still isn't working, email ipv6@he.net and let them know...they just need to refresh some things on their end

[pcreager]

Yup, looks good here too:

Code: [Select]

$ dig +noall +ans mx domblogger.net
domblogger.net. 604800 IN MX 10 mail.domblogger.net.
$ dig +noall +ans aaaa mail.domblogger.net
mail.domblogger.net. 604800 IN AAAA 2600:3c00::f03c:91ff:fe93:ee82
$ dig +noall +ans -x 2600:3c00::f03c:91ff:fe93:ee82
2.8.e.e.3.9.e.f.f.f.1.9.c.3.0.f.0.0.0.0.0.0.0.0.0.0.c.3.0.0.6.2.ip6.arpa. 86400 IN PTR mail.domblogger.net.

Just a friendly note, though: your TTLs are way too long.  If/when you ever need to change your IP or your mail host, it would take a week for it to propagate to all corners of the Internet.

[DOMBlogger]

Thanks - I'm actually soon going to be running NSD for all my domains except for one.

I'm presently in the process of coding an admin interface that will meet my specific needs (though not everything NSD is capable of), and I am planning to use a 24 hour TTL as default, so when that's up, the TTL issue will be resolved.

For this exercise, I just used Linode's default.

[pcreager]

Thanks - I'm actually soon going to be running NSD...

Um, why?  If you want experience running DNS that's applicable in the real world, I say stick with BIND.