*.mail.protection.outlook.com Missing AAAA IPv6

Anonymous
2021-12-30T09:45:02+00:00

Hi

The current MX for Office365/Microsoft365 is (currently) always domain.mail.protection.outlook.com.

;; QUESTION SECTION:

;x.mail.protection.outlook.com. IN ANY

;; ANSWER SECTION:

x.mail.protection.outlook.com. 10 IN A 104.47.24.36

x.mail.protection.outlook.com. 10 IN A 104.47.25.36

Here we see the lack of AAAAWhy?And how do we fix it?Is there any other MX available with IPv6 enabled that we can use?

Dear Microsoft, please start accepting that there is IPv6 only hosts now!

And the same goes for the nameservers missing AAAA.

;; QUESTION SECTION:

;mail.protection.outlook.com. IN NS

;; ANSWER SECTION:

mail.protection.outlook.com. 9 IN NS ns1-proddns.glbdns.o365filtering.com.

mail.protection.outlook.com. 9 IN NS ns2-proddns.glbdns.o365filtering.com.

;; ADDITIONAL SECTION:

ns1-proddns.glbdns.o365filtering.com. 29 IN A 104.47.72.81

ns1-proddns.glbdns.o365filtering.com. 29 IN A 104.47.16.17

ns2-proddns.glbdns.o365filtering.com. 29 IN A 104.47.72.81

ns2-proddns.glbdns.o365filtering.com. 29 IN A 104.47.15.17

With M-21-07 in mind, there can't be any Agencies as customers, or is MS just hiding the v6 support?

I have found https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/support-for-anonymous-inbound-email-messages-over-ipv6

Not sure what is meant with Anonymous here, but is that what we need to do, and if so, how do I reach the right support people?

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

6 answers

Sort by: Most helpful
  1. Anonymous
    2022-01-07T06:38:16+00:00

    After again being asked to have SPF records (which only relates to the sender, and is not specific to IPv6)
    The DNS name for receiving MX now has AAAA records.

    Answer:
    The correct answer here unfortunately is, open a support ticket.
    Be clear which domain it is that you want the MX record to have AAAA records for.
    Also include that PTR+SPF/DKIM records of sender, can not be controller by the receiver (us).

    > If you would like to have IPv6 enabled for any domain, please raise a ticket with a request for the "PG team to enable IPv6".

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-12-31T13:45:23+00:00

    Dear C Nilsson,

    Very sorry for misunderstanding! Thanks for your patience and understanding!

    Based on your question, please refer to this:

    ![](https://learn-attachment.microsoft.com/api/attachments/51ce92b3-354b-43ae-a533-95c73e94ad3f?platform=QnA

    And please kindly also refer to this article and get more details: Office 365 URLs and IP address ranges - Microsoft 365 Enterprise | Microsoft Docs

    In addition, to help you better, I would like to confirm that what is your scenario? Is it to add a domain or just want to modify the MX record?

    Hope this can help you, the new year is coming, I wish you a happy new year and all the best!

    Best regards,

    Kerry

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-12-30T13:56:44+00:00

    This tries to explain how to add an MX record to a DNS (in a really horrible and hard to understand way) when adding/activating a domain in Microsoft365, and not using the TXT record method. - which has nothing to do with my request.

    Not even sure where to begin, I was hoping that there was a bit higher technical level here!
    My questions is actually extremely clear from the beginning. How ever it does require some understanding of what DNS is, how it works, and also what IPv6. I was hoping that I, as a customer, would not have to explain this part to technical support.

    The question is how to get IPv6 support on the domain.mail.protection.outlook.com. that is used as MX record.
    If you are on Windows and want to verify this use:

    >nslookup domain.mail.protection.outlook.com.

    Name: domain.mail.protection.outlook.com

    Addresses: 104.47.58.138

          104.47.57.138 
    

    We need it to return at least one IPv6 address, the one with colons ":" and not dots "." (not sure why I need to explain how an IPv6 address looks like, but oh well)

    Here is an example:

    >nslookup v4v6.ipv6-test.com

    Name: v4v6.ipv6-test.com

    Addresses: 2001:41d0:701:1100::29c8

          51.75.78.103
    

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-01-01T10:53:34+00:00

    Sending server can be IPv6 only > "Dear Microsoft, please start accepting that there is IPv6 only hosts now!"

    Receiving server must be able to accept email from IPv6 only senders.

    If the MX servers are Legacy-v4 only (as is the case with current x.mail.protection.outlook.com) it means that IPv6 only servers can't send emails to the domain.

    You are listing IP-Ranges that might be used by SMTPs in X.mail.protection.outlook.com

    Which is a good start. Now we just need a hostname that points to one of those. (You can't point a hostname to a range)

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-12-30T13:31:50+00:00

    Dear C Nilsson,

    Thanks for choosing Microsoft community!

    I have carefully read your description and done some research, please kindly refer to following suggestions:

    Maybe you can refer to the MX record as below:

    This MX record's Priority must be the highest of all existing MX records for the domain. Otherwise, it can interfere with sending and receiving email. You should delete this records as soon as domain verification is complete.

    Make sure that the fields are set to the following values:

    Record Type: MX

    Priority: Set to any large value not used already.

    Host Name: @

    Points to address: Copy the value from the admin center and paste it here.

    TTL: 3600 (or your provider default)

    I also have shared information in private message regarding your mentioned scenario, please click here PI(personal information) to get more details.

    Hope this can help you, if there is any deviation in my understanding, please forgive me and provide me with more details, I am more than willing to continue to help you!

    Best regards,

    Kerry

    Was this answer helpful?

    0 comments No comments