Sbs 2016 dns not updating

09-Oct-2017 23:25 by 3 Comments

Sbs 2016 dns not updating

This record points the Autodiscover service to a specific location for getting the configuration it needs.

The issues you may run into are specifically limited to Exchange Organizations that have a Domain Name that uses a non-public TLD like domain.local, or a public domain name that they don’t actually own and can’t use externally as well.It will take the following pattern when checking for Autodiscover services: 1.Autodiscover will attempt to find the Autodiscover configuration XML file at the domain name of the SMTP address used in configuration (because internal domain computers configure themselves automatically by default, this matches the Internal Domain.With Exchange 20, you will get a Certificate error every time you open Outlook.Generally, this error will state that the name on the certificate is not valid.As a result, you won’t be able to get a valid SSL certificate that allows domain.local as a SAN.

This means that the automated steps Exchange uses for Autodiscover configuration will always fail on an Internal domain with a name that is not publicly accessible or not owned.

For example, the first place autodiscover looks is https://domain.com/Autodiscover/for external addresses.

Change with domain.local for what Exchange looks for on Internal clients. If the autodiscover record is not found at domain.com/domain.local, the server will attempt to connect to https://autodiscover.domain.com/Autodiscover/(replace with domain.local for internal).

By now, anyone who has managed, deployed, or worked with an Exchange 2007 or later environment should be familiar with Autodiscover.

If you aren’t yet, I’ll give a short Explanation of what it is and how it works.

This usually involves adding Subject Alternate Names to the SSL certificate you use for your Exchange Server to allow the many host names used to be authenticated with the certificate.