What specific DNS records need to be added when setting up a custom domain in Google Domains, and what information should they contain?
When setting up a custom domain in Google Domains for a Webflow CMS and eCommerce site, it is essential to configure several DNS (Domain Name System) records accurately. These DNS records serve as the backbone of your domain's internet presence, directing traffic to the appropriate web servers and ensuring that various services, such as email and web hosting, function correctly. The primary DNS records that need to be configured are A records, CNAME records, and optionally, TXT records for verification purposes. Below is a detailed explanation of each type of DNS record, including what information they should contain and how they contribute to the seamless operation of your custom domain.
1. A Records (Address Records):
A records are used to map your domain or subdomains to the IP addresses of the web servers hosting your site. These records are important for directing web traffic to the correct server. When setting up A records for Webflow, you typically need to add multiple A records pointing to different IP addresses provided by Webflow. This redundancy ensures that your site remains accessible even if one of the IP addresses becomes unavailable.
Example:
Name/Host/Alias: @ Type: A TTL: 3600 (1 hour) Data/Value: 75.2.70.75 Name/Host/Alias: @ Type: A TTL: 3600 (1 hour) Data/Value: 99.83.190.102
In this example, the '@' symbol represents the root domain (e.g., example.com). The TTL (Time to Live) value specifies how long the DNS resolver should cache the information before querying the DNS server again. The IP addresses (75.2.70.75 and 99.83.190.102) are the servers where your Webflow site is hosted.
2. CNAME Records (Canonical Name Records):
CNAME records are used to alias one domain name to another. This is particularly useful for pointing subdomains to the Webflow servers. When setting up a custom domain in Webflow, you will often need to create a CNAME record for the 'www' subdomain, pointing it to Webflow's proxy server.
Example:
Name/Host/Alias: www Type: CNAME TTL: 3600 (1 hour) Data/Value: proxy-ssl.webflow.com
In this example, the 'www' subdomain (e.g., www.example.com) is pointed to Webflow's proxy server (proxy-ssl.webflow.com). This ensures that when users visit the 'www' version of your domain, they are directed to Webflow's servers.
3. TXT Records (Text Records):
TXT records are used to store text information in the DNS. They are often used for domain verification and email security purposes. When connecting a custom domain to Webflow, you may need to add a TXT record to verify domain ownership. Webflow will provide you with the specific value to include in the TXT record.
Example:
Name/Host/Alias: @ Type: TXT TTL: 3600 (1 hour) Data/Value: webflow-verification=1234567890abcdef
In this example, the '@' symbol again represents the root domain. The data value (webflow-verification=1234567890abcdef) is a unique token provided by Webflow for domain verification purposes.
4. MX Records (Mail Exchange Records):
If you are using Google Workspace (formerly G Suite) or another email service provider, you will need to configure MX records to route email correctly. These records specify the mail servers responsible for receiving email on behalf of your domain.
Example (for Google Workspace):
Name/Host/Alias: @ Type: MX TTL: 3600 (1 hour) Data/Value: 1 aspmx.l.google.com. Name/Host/Alias: @ Type: MX TTL: 3600 (1 hour) Data/Value: 5 alt1.aspmx.l.google.com. Name/Host/Alias: @ Type: MX TTL: 3600 (1 hour) Data/Value: 5 alt2.aspmx.l.google.com. Name/Host/Alias: @ Type: MX TTL: 3600 (1 hour) Data/Value: 10 alt3.aspmx.l.google.com. Name/Host/Alias: @ Type: MX TTL: 3600 (1 hour) Data/Value: 10 alt4.aspmx.l.google.com.
In this example, the '@' symbol represents the root domain. The priority values (1, 5, 10) determine the order in which mail servers are used. Lower values have higher priority.
5. Additional Optional Records:
Depending on your specific needs and services, you may need to configure additional DNS records, such as SRV (Service) records for certain applications or SPF (Sender Policy Framework) records to improve email deliverability and prevent spoofing.
Example of an SPF record:
Name/Host/Alias: @ Type: TXT TTL: 3600 (1 hour) Data/Value: v=spf1 include:_spf.google.com ~all
In this example, the SPF record specifies that only mail servers listed in the SPF record for Google (v=spf1 include:_spf.google.com) are authorized to send email on behalf of the domain. The '~all' mechanism indicates that mail from unauthorized servers should be marked as suspicious.
To summarize, setting up a custom domain in Google Domains for a Webflow site involves configuring several DNS records, including A records, CNAME records, TXT records, and optionally MX and SPF records. Each record type serves a specific purpose and must be accurately configured to ensure the proper functioning of your website and associated services. By following the guidelines and examples provided, you can ensure that your custom domain is correctly connected and operational.
Other recent questions and answers regarding Connecting a custom domain:
- What steps should be taken to ensure that the staging domain is not indexed by search engines when publishing the site?
- Why is it important to select the "www" version of the domain as the default, and how can this be done in Webflow?
- How can you verify that a hosting plan has been added to your Webflow project before connecting a custom domain?
- What are the initial steps to take when connecting a custom domain if the domain registrar is Google Domains?