Configuring Microsoft 365 DKIM Records on Google Domains

Recently I was attempting to configure mail security for a client, but for some strange reason the CNAME records for 365 DKIM were being extremely stubborn. I found that the UI within G Domains is a little picky about how it will accept the values that 365 is asking you to provide. It will also attempt to auto-qualify your record value if it does not include a trailing period.

  1. Go to DNS settings in G Domains.
  2. Scroll to Custom resource records.
  3. In the Name (also called Host) field, enter the value suggested by 365.
    NOTE: The UI will not allow you to type a period in this field. You can however copy-paste the value in or edit it after you have saved the record to include it.
    selector1._domainkey
  4. Change the record type to CNAME.
  5. Leave the TTL value at 1hr/3600sec.
  6. In the Data field, enter the value that correlates to your custom domain. In the below example, I'm pretending that my custom domain name is "domainname.net" and my initial domain is the generated one I received when signing up for 365, "domainname.onmicrosoft.com".
    NOTE: Be sure to include the period (.) at the end of the name.
    selector1-domainname-com._domainkey.domainname.onmicrosoft.com.
  7. Click Add.
  8. Repeat steps 3-7 to add a record for selector2.
  9. Propagation is usually fairly quick - about 15mins, but can take up to 48hrs. You can verify that you're ready to enable DKIM on your custom domain by:
    1. Going to MXToolbox CNAME checker.
    2. Query the DKIM record as below:
      selector1._domainkey.domainname.com

Comments

Post a Comment

Popular posts from this blog

Continuously Monitor Folder for New Files with PowerShell as a WindowsService

Recently encountered an old-school application that used a cobbled-together external service to generate reports and deliver to end-users in PDF format. Unfortunately, this service didn't have any error handling other than dropping the intended source content into a flat file in an error directory on the local disk. No monitoring, no notification, just fail and pretend it never happened. As these reports are critical to end users, I needed a way to monitor this directory for any new files and notify someone so that the report could be manually re-generated. After some initial Googling, I decided a quick PowerShell script would be the easiest method to continuously monitor the directory and fire off a notification when a new file is found. I'm admittedly an extreme PowerShell newbie, so I'm sure there are better, cleaner ways to do this, but this works nicely and is stable enough for now until my legacy system is retired in a few months. The below PowerShell script will inst
Read more

Unprotect All Excel Sheets for All Workbooks in a Directory

This Excel macro came in very handy when I had a set of workbooks in a folder (and subfolders) that all needed unprotected before running another macro to combine all of the workbooks into a single file. Be sure to update the bolded variables below.  Source . Const cStartFolder = " C:\Documents and Settings\UserName\My Documents\Spreadsheets " 'no slash at end Const cFileFilter = " *.xlsx " Const cPassword = " CleverPassword " 'use empty quotes if blank Sub UnprotectAllWorksheets() Dim i As Long, j As Long, arr() As String, wkb As Workbook, wks As Worksheet ExtractFolder cStartFolder, arr() On Error Resume Next j = -1: j = UBound(arr) On Error GoTo 0 For i = 0 To j Set wkb = Workbooks.Open(arr(i), False) For Each wks In wkb.Worksheets wks.Unprotect cPassword Next wkb.Save wkb.Close Next End Sub Sub ExtractFolder(Folder As String, arr() As String) Dim i As Long, objF
Read more

ChromeOS Flow by Hexxeh Install to HDD

I finally decided to pull out the netbook again and check out the ChromeOS release of Flow by Hexxeh . I got the image downloaded, untar'd and imaged to the thumbdrive. Now comes the part when I want to actually install it to the solid-state disk in my Asus EeePC, right? Well, online sources said to just run /usr/sbin/chromeos-install and it would be taken care of. It kept erroring with "Attempt to install to a removable device: /dev/sda". Of course, this is my thumbdrive so that would make sense. Since it took me some digging to figure this one out, I thought I'd throw up the solution here to make it a little more visible on the Interwebs. Instead, run this command: /usr/sbin/chromeos-install /dev/sdb This should work if your internal device is at least 8gb. Unfortunately for me, mine is 4gb and my source media is 2gb. Instead, I ended up just copying the entire live image from my thumbdrive to the hard drive. Whatever works, right? Run this command instead of the ab
Read more