Can I use Google Workspace or Microsoft 365 with GA.NU?

Yes. GA.NU fully supports connecting your .ga.nu subdomain to third‑party email providers like Google Workspace and Microsoft 365. You simply add the DNS records those providers require (MX, TXT, CNAME) in the GA.NU Domain Manager for your subdomain (for example, acme.ga.nu).

This guide explains the process, provides practical examples, and highlights common pitfalls.

Before you begin

Decide which provider you will use for email on the specific subdomain (e.g., user@acme.ga.nu). You should not point MX records for the same subdomain to two different providers at the same time.
If you plan to use different providers for different subdomains (e.g., mail.acme.ga.nu on Google and corp.acme.ga.nu on Microsoft), that’s fine—configure each subdomain independently.
Have access to:
- GA.NU Domain Manager (to add DNS records)
- Your Google Workspace or Microsoft 365 admin console (to get verification, MX, SPF, DKIM, and other settings)

How it works (high-level)

Add your GA.NU subdomain (e.g., acme.ga.nu) in your provider’s admin console.
Complete domain verification by adding a TXT record in GA.NU.
Add MX records to route mail to your provider.
Add SPF, DKIM, and DMARC for better deliverability and security.
Wait for DNS propagation and then test.

Set up Google Workspace

1) Verify the domain

Google will give you a TXT record like:

Name/Host: @ (or leave blank if your DNS UI implies @)
Type: TXT
Value: google-site-verification=XXXXXXXXXXXX

Add this in GA.NU, save, and click Verify in Google Admin.

2) Add MX records for Gmail

Add the following MX records for acme.ga.nu:

@  MX  1   ASPMX.L.GOOGLE.COM.
@  MX  5   ALT1.ASPMX.L.GOOGLE.COM.
@  MX  5   ALT2.ASPMX.L.GOOGLE.COM.
@  MX 10   ALT3.ASPMX.L.GOOGLE.COM.
@  MX 10   ALT4.ASPMX.L.GOOGLE.COM.

Notes:

Keep the trailing dot on hostnames if your DNS UI expects FQDNs.
TTL can be 3600 (1 hour) or provider-recommended.

3) Add SPF

Add a TXT record for SPF to authorize Google to send email for your domain:

@  TXT  "v=spf1 include:_spf.google.com ~all"

4) Enable DKIM

In Google Admin, generate a DKIM key (default selector: google), then add the TXT record:

google._domainkey  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."

After DNS propagates, return to Google Admin and click Start authentication.

5) Add DMARC (optional but recommended)

Add a TXT record at _dmarc:

_dmarc  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@acme.ga.nu; pct=100"

Adjust the policy (p=none/quarantine/reject) and reporting addresses to your needs.

Set up Microsoft 365

1) Verify the domain

Microsoft 365 will provide a TXT record like:

Name/Host: @
Type: TXT
Value: MS=ms########

Add this in GA.NU, save, and click Verify in Microsoft 365.

2) Add MX records for Exchange Online

Microsoft will provide an MX target unique to your tenant (example format shown):

@  MX  0  acme-ga-nu.mail.protection.outlook.com.

Use the exact target and priority shown in your Microsoft 365 admin center.

3) Add SPF

Add a TXT record:

@  TXT  "v=spf1 include:spf.protection.outlook.com -all"

(-all is stricter; you can use ~all during initial testing.)

4) Enable DKIM

Microsoft 365 typically uses two CNAME records. After enabling DKIM in the Security/Exchange admin center, you’ll be given two records similar to:

selector1._domainkey  CNAME  selector1-acme-ga-nu._domainkey.acme.onmicrosoft.com.
selector2._domainkey  CNAME  selector2-acme-ga-nu._domainkey.acme.onmicrosoft.com.

Use your exact values (they depend on your initial onmicrosoft.com domain and your subdomain).

5) Autodiscover (optional)

For legacy/Outlook autodiscover, add:

autodiscover  CNAME  autodiscover.outlook.com.

6) Add DMARC (optional but recommended)

_dmarc  TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@acme.ga.nu; pct=100"

Where to add records in GA.NU

Log into your GA.NU account
Open the Domain Manager for your subdomain (e.g., acme.ga.nu)
Add or edit DNS records exactly as provided by your email provider
Save changes and wait for DNS propagation

If your subdomain’s DNS is delegated to an external DNS provider, make the changes there. Not all GA.NU plans support delegation—contact support if you’re unsure.

Propagation and testing

DNS changes typically propagate within minutes but can take up to 24–48 hours globally.
Use these tools to verify:
- dig or nslookup: check MX/TXT/CNAME records
- Google Admin: Domain verification, DKIM “Start authentication”
- Microsoft 365 Admin: Domain status, DKIM status
- Mail sending tests: mail-tester.com, Gmail/Outlook delivery checks

Example checks:

# Check MX
nslookup -type=mx acme.ga.nu

# Check TXT (SPF)
nslookup -type=txt acme.ga.nu

# Check DKIM
nslookup -type=txt google._domainkey.acme.ga.nu
nslookup -type=cname selector1._domainkey.acme.ga.nu

Common pitfalls

Mixing MX providers: Only point MX for a single subdomain to one provider at a time.
Incorrect record names: Some DNS UIs expect @ for the root of your subdomain; others leave the name blank.
Missing trailing dots: If your DNS system requires fully qualified names with trailing dots, include them (e.g., ASPMX.L.GOOGLE.COM.).
SPF syntax errors: You can have only one SPF TXT record per name. Combine mechanisms if needed.
DKIM not enabled: Adding records isn’t enough—remember to click “Start authentication” in your provider’s admin.
Conflicting CNAME/A records: You cannot create both an A and CNAME for the same name. Follow your provider’s guidance.

Can I use both Google and Microsoft at the same time?

For the same subdomain (e.g., acme.ga.nu), choose one provider for MX routing.
You can use different subdomains for different providers (e.g., mail.acme.ga.nu on Google, corp.acme.ga.nu on Microsoft), and create user addresses accordingly.

Need help?

If you’re unsure which records to add or you don’t see the DNS options you need, contact GA.NU Support with:

Your subdomain (e.g., acme.ga.nu)
The exact records your provider gave you
Any error messages from Google Workspace or Microsoft 365

We’ll help you get set up quickly.