Office365DnsChecker

1.1.0

Checks a domain's Office 365 DNS records for correctness.

Minimum PowerShell version

5.1

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name Office365DnsChecker -RequiredVersion 1.1.0

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name Office365DnsChecker -Version 1.1.0

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

(c) 2019-2023 Colin Cogle. All rights reserved. Licensed under the GPL version 3.

Package Details

Author(s)

  • Colin Cogle <colin@colincogle.name>

Tags

Microsoft365 Office365 365 ExchangeOnline SkypeForBusinessOnline MicrosoftTeams DNS AzureAD AAD SPF DKIM ExO Exchange Teams ExchangeHybrid 21Vianet

Functions

Test-Office365DNSRecords Test-AzureADRecords Test-ExchangeOnlineRecords Test-TeamsRecords Test-AzureADClientConfigurationRecord Test-AzureADEnterpriseEnrollmentRecord Test-AzureADEnterpriseRegistrationRecord Test-ExchangeOnlineAutodiscoverRecord Test-ExchangeOnlineDkimRecords Test-ExchangeOnlineMxRecord Test-ExchangeOnlineSenderIdRecord Test-ExchangeOnlineSpfRecord Test-TeamsAutodiscoverRecord Test-TeamsSipCnameRecord Test-TeamsSipSrvRecord Test-TeamsSipFederationSrvRecord

PSEditions

Core Desktop

Dependencies

This module has no dependencies.

Release Notes

- NEW: Add support for checking DNS records for Office 365 hosted by 21Vianet.
- ENHANCEMENT: The Azure AD client configuration record check now passes if the msoid record is missing.  As of early 2023, this DNS record is only required to be set when Office 365 is managed by 21Vianet.
- FIXED: On a small number of configurations, DNS resolution would enter an infinite loop.  This would happen if you were running macOS or Linux, and had an alternative implementation of Resolve-DnsName.  Now, the only cmdlet we'll use is DnsClient\Resolve-DnsName before falling back to the built-in DNS resolver.
- Code cleanup.
- The default branch was renamed from 'master' to 'main'.

FileList

Version History

Version Downloads Last updated
2.0.1 1,041 2/14/2024
2.0.0 202 1/19/2024
1.1.0 (current version) 200 6/1/2023
1.0.3 396 7/26/2021
1.0.2 16 7/26/2021
1.0.1 206 3/30/2020
1.0.0 85 11/12/2019
Show more