Skip to content

Latest commit

 

History

History
75 lines (57 loc) · 5.05 KB

README.md

File metadata and controls

75 lines (57 loc) · 5.05 KB
Raw

PowerShell Gallery Version (including pre-releases) PowerShell Gallery

Office365DnsChecker

Office365DnsChecker will check one or more domains, to make sure that their current DNS records are set up correctly and completely for Office 365.

Office365DnsChecker logo

System Requirements

This module requires Windows PowerShell 5.1 or greater. It works great on PowerShell 7, and supports constrained language mode.

Additionally, Linux users will need to install the app dig (part of bind-utils). It is installed by default on macOS (at least in High Sierra).

Installation

You can clone this repository and put it in your $PSModulePath, or grab it from PSGallery:

Install-Module -Name Office365DnsChecker

Usage

You can check all applicable Office 365 DNS records at once with the cmdlet Test-Office365DnsRecords:

PS C:\> Test-Office365DnsRecords "contoso.com"

These cmdlets also accept pipeline input. If you're logged into Exchange Online, use the following command to test all of your organization's domains.

PS C:\> Get-AcceptedDomain | Test-Office365DnsRecords

Advanced Usage

You can also check individual services:

  • Test-EntraIDRecords
  • Test-ExchangeOnlineRecords
  • Test-TeamsRecords (or Test-SkypeForBusinessOnlineRecords)

Or, you can even check individual DNS records:

  • Test-EntraIDClientConfigurationRecord to check the msoid CNAME.
  • Test-EntraIDEnterpriseEnrollmentRecord to check the enterpriseenrollment CNAME.
  • Test-EntraIDEnterpriseRegistrationRecord to check the enterpriseregistration CNAME.
  • Test-ExchangeOnlineAutodiscoverRecord to check both the existence of the autodiscover CNAME, and the non-existence of _autodiscover._tcp SRV records.
  • Test-ExchangeOnlineDkimRecords to check the selector1 and selector2 DKIM records.
  • Test-ExchangeOnlineMxRecord to check the domain's MX record(s) and whether or not they support DANE.
  • Test-ExchangeOnlineSenderIdRecord to check the domain's Sender ID record, if present.
  • Test-ExchangeOnlineSpfRecord to check the domain's SPF TXT record.
  • Test-TeamsAutodiscoverRecord to check the lyncdiscover CNAME.
  • Test-TeamsSipCnameRecord to check the sip CNAME.
  • Test-TeamsSipSrvRecord to check the _sip._tls SRV record(s).
  • Test-TeamsSipFederationSrvRecord to check the _sipfederationtls._tcp SRV record(s).

Identifying problems

When you run one of this module's commands, the corresponding DNS records are retrieved and evaluated. In case of an incorrect record, a warning or an error may be printed to the screen, telling you which records are wrong or missing.

If an error is printed, you can retrieve the error object through the $error automatic variable, just like PowerShell supports normally:

$error[0].ErrorDetails

Getting help for resolving problems

In addition, basic steps to resolving the error may be available through the information pipeline. You can make this information visible by regular means such as specifying -InformationAction Continue, setting $InformationPreference, or redirecting the information pipeline (six). This information is also available in the error object's details.

# this works.
Test-Office365DnsRecords "contoso.com" -InformationAction Continue

# this also works.
Test-Office365DnsRecords "contoso.com" 6> howtofixcontoso.txt

# this works, too.
$error[0].ErrorDetails.RecommendedAction

While the included one- or two-sentence tips may be useful for giving Office 365 administrators some idea on how to fix any DNS problems, you should still consult the Microsoft 365 Admin Center's Domains page, which will tell you all but exactly how to fix your DNS records in common scenarios.

In some cases, DNS records may intentionally be incorrect -- for example, if you have a third-party spam filter sitting in front of Exchange Online that requires custom MX records; or, if you have an on-premises Skype for Business Server that requires your Teams-/Skype-related DNS CNAME records to be incorrect intentionally. Please consult your IT department or your local MCSE to make sure that following this module's generic advice won't interrupt your company's operations.