Google Domains DNS Setup Guide

How to Set Up DNS Records on Google Domains

Google Domains (now Squarespace Domains) offers straightforward DNS management with Google's reliable infrastructure. This guide walks through setting up DNS records in Google Domains, from website hosting to email configuration.

Step-by-Step Setup Guide

1. Access Google Domains Console Log into domains.google.com with your Google account.
   • Click on your domain name from the 'My domains' list
   • Select 'DNS' from the left sidebar menu
   • Ensure 'Use Google Domains nameservers' is selected (not custom)
   • If using custom nameservers, manage DNS at that provider instead
2. Navigate to Resource Records Scroll down to the 'Resource records' section on the DNS page.
   • You'll see existing records like @ pointing to Google parking
   • Default records include synthetic records for Google services
   • Click 'Manage custom records' to add or edit DNS entries
3. Add Custom DNS Record Click 'Create new record' to add a DNS entry.
   • Enter hostname (leave blank for @ root domain, or type subdomain)
   • Select Type from dropdown (A, AAAA, CNAME, MX, TXT, etc.)
   • Set TTL (default 3600 seconds, or custom from 300-86400)
   • Enter Data/Value (IP address, hostname, text content, or priority for MX)
   • Click 'Add' to save the record
4. Verify Propagation DNS changes on Google Domains typically propagate quickly.
   • Google Domains updates authoritative servers within minutes
   • Global propagation depends on TTL and DNS caching (typically 1-4 hours)
   • Use ReviewMyDNS to verify changes across 50+ global DNS servers
   • Flush local DNS cache to see updates on your device immediately

Common DNS Record Types on Google Domains

• A Record: Points your domain to an IPv4 address. Leave host blank for root domain (example.com) or enter subdomain name (www, blog). Required to connect domain to web hosting server. Host: (blank for @), Type: A, TTL: 3600, Data: 192.0.2.1
• CNAME Record: Creates an alias pointing to another domain name. Cannot be used on root domain - use A record instead. Common for www subdomain or third-party service integrations like email providers. Host: www, Type: CNAME, TTL: 3600, Data: example.com
• MX Record: Directs email to mail server. Data field includes priority (lower = higher priority) followed by server hostname. Add multiple MX records with different priorities for email redundancy. Host: (blank), Type: MX, TTL: 3600, Data: 10 mail.example.com
• TXT Record: Stores text data for SPF email authentication, domain verification, DKIM signatures, and DMARC policies. Essential for email deliverability and proving domain ownership to third-party services. Host: (blank), Type: TXT, TTL: 3600, Data: v=spf1 include:_spf.google.com ~all

Troubleshooting Common Issues

• DNS changes not visible after 1 hour: Google Domains typically propagates within 15-30 minutes to their nameservers. Global propagation to ISPs can take longer (up to 24-48 hours) due to DNS caching. Flush your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac). Use our DNS propagation checker to see which servers have updated records.
• Cannot use CNAME on root domain: DNS specification prohibits CNAME records on root domains (@). Google Domains requires an A record pointing to an IP address for root domains. If your hosting provider only gives a CNAME, ask for the IP address to use in an A record, or consider using Cloudflare's CNAME flattening.
• Email stopped working after changing DNS: Verify you didn't delete existing MX records during DNS changes. Email requires MX records pointing to mail servers, plus SPF and DKIM TXT records. Check Google Workspace or email provider documentation for correct MX values. Email propagation can take 2-6 hours globally.
• Website shows Google parking page instead of my site: This indicates A records are still pointing to Google's parking IP (typically 216.239.32.21). Update or delete the @ A record to point to your hosting provider's IP address. Changes appear within 30 minutes on Google's servers, but ISP caching may delay 1-4 hours.

Frequently Asked Questions

• What happened to Google Domains? Google sold Google Domains to Squarespace in June 2023. Existing Google Domains customers can continue using the service with the same features and pricing. Domains are gradually being migrated to Squarespace, but DNS management functionality remains unchanged during the transition.
• What TTL should I use on Google Domains? The default 3600 seconds (1 hour) is suitable for most stable DNS records. Use lower TTL (300-600 seconds) before making planned changes for faster propagation. Higher TTL (14400-86400 seconds) reduces DNS query load and improves performance for rarely-changing records. Adjust TTL before changes, then increase after propagation.
• How long does Google Domains DNS propagation take? Google Domains updates their authoritative nameservers within 10-30 minutes. Complete global propagation varies from 1-4 hours typically, up to 48 hours in rare cases. Propagation time depends on previous TTL values and ISP DNS caching policies. Monitor real-time propagation with our global DNS checker tool.
• Can I use external nameservers with Google Domains? Yes! In DNS settings, select 'Use custom name servers' and enter nameservers from providers like Cloudflare or your hosting company. Nameserver changes take 24-48 hours to propagate. Once changed, manage all DNS records at the external provider. You can switch back to Google nameservers anytime.