#IPv6 support for services doesn't appear to have changed in the last decade. ISPs may have deployed it in the plumbing but that hasn't translated to services.
Domain name service does best because only one name server needs to be reachable via IPv6 to pass the test and a number of domains use a 3rd party that supports IPv6. Mail delivery and Web site have been largely static for a decade. #DNSSEC is even worse than IPv6 and I suspect that DANE wouldn't be noticeable.
@markrprior Supposedly, one can open a ticket to get AAAA records added to one’s #ExchangeOnline MX endpoint (*.mail.protection.outlook.com). I tried that with a customer once, but my Microsoft CSP partner at the time was like “…what?”
Whether or not this will change with the new #DNSSEC-signed ..mx.microsoft MX records remains to be seen.
@markrprior Since they can accept mail over IPv6 (but don’t want to), they must have working anti-spam tools. They note that mail over #IPv6must have a PTR record and pass either SPF or DKIM, the same requirement Google Woekspace enforces.
In the EAC, I don’t see anything specifically tied to IPv4 besides the occasional text box that doesn’t accept colons (looking at you, Receive Connectors). In contrast, the on-premises version of Exchange Server supports IPv6 rather well.
Add comment