When setting up a subdomain, what A record should I use, and when should I use a CNAME?

Marketer from Email Geeks explains that even if you want to use the subdomain for email tracking, ESPs will probably ask for a CNAME, not an A record. This would have to be a sub-domain of this subdomain (like t.investors.audiencepoint.com), because you can't have a CNAME along with any other record at the same level.

Email marketer from Linode Docs responds when you use a CNAME, you can point a subdomain to another domain name. This is helpful if the IP address of the target resource changes over time. If a service you use makes an IP change, you don't have to update DNS records directly; only the record for the canonical name needs to be changed.

Marketer from Email Geeks shares that ESP documentation usually has exactly how to do and what to point to. Even the setup process will guide you as you set up, including what to put in DNS.

Marketer from Email Geeks explains that if an A record is required, use the IP of one of your web servers and to never let your domain name point to something you don't own or have a contractual relation with.

Email marketer from Webmaster World explains CNAME records are often used to point a subdomain to a third-party service, such as a content delivery network (CDN) or an email marketing platform. The CNAME would point to the service's domain, and the service manages the underlying IP address. This allows the service to change its infrastructure without requiring you to update your DNS records.

Email marketer from GoDaddy Help responds if your domain name or subdomain needs to resolve to a static IP address, use an A record. This tells the internet where to find the server hosting your website or application.

Email marketer from DNSimple explains that A records are for pointing your domain or subdomain directly to an IP address. CNAME records point your domain or subdomain to another domain name. Use A records for your primary website and CNAME records for services or applications that might change locations.

Email marketer from Name.com Support explains if your hosting provider instructs you to use a CNAME record to connect your domain to their servers, follow their instructions. They use CNAMEs for flexibility and to manage their infrastructure without you needing to update your DNS settings frequently.

Email marketer from Hostinger Tutorials suggests you should typically use an A record for your primary domain to point to your web server's IP. Then, use CNAME records for subdomains (like blog.example.com or shop.example.com) to point to specific services or applications.

Marketer from Email Geeks shares that ideally, the subdomain should point to your website, and your website would redirect from the subdomain to www or something.

Email marketer from Cloudns responds that CNAMEs allow for more flexibility when the target resource changes IP addresses. Instead of updating the A record, only the target domain's IP needs to be updated. This is useful for content delivery networks (CDNs) or cloud services, where the underlying infrastructure may change.

Email marketer from Namecheap responds if you have a website hosted on a server with a dedicated IP address, you need to create an A record to point your domain or subdomain to that IP. This tells browsers where to find your website's files.

Email marketer from Stack Overflow shares that A records are typically used for the main domain or subdomains that need a direct IP address, like a web server. If your subdomain hosts a website, it will likely need an A record pointing to the server's IP.

Email marketer from Reddit shares when setting up a subdomain for email marketing (e.g., mail.example.com), you'll typically use a CNAME record to point it to your email service provider (ESP). The ESP will provide the target domain for the CNAME record. This allows them to handle the technical details of routing your email.

Expert from SpamResource explains that when setting up a subdomain for email sending (e.g., mail.example.com), it's best practice to use a CNAME record to point it to your email service provider (ESP). The ESP manages the A records, handling IP changes and infrastructure. This is crucial for maintaining deliverability and avoiding technical complexities.

Expert from Word to the Wise responds if you are setting up a subdomain for a specific service, like email or a CDN, use a CNAME record. The service provider will manage the underlying IP addresses, and you won't need to update your DNS settings every time the service's IP changes. CNAME records are more flexible for services that may change locations.

Documentation from AWS Route 53 explains A records point a domain name to an IPv4 address. CNAME records, on the other hand, point a domain name to another domain name. The choice depends on whether you need to point directly to an IP or to another domain name that might change IPs.

Documentation from Microsoft explains A records map a domain name to an IPv4 address, which is suitable for websites and services hosted on Azure Virtual Machines or other resources with a static IP. CNAME records map a domain name to another domain name. Use CNAME records for services hosted elsewhere that might change IP addresses, or for load balancing scenarios. This is helpful for email delivery when using external services.

Documentation from Cloudflare explains that an A record maps a domain name to an IPv4 address, while a CNAME record maps an alias domain name to a canonical domain name. Use A records when you need to point your domain or subdomain directly to an IP address. Use CNAME records when you want to alias one domain to another, allowing for easier management and updates.

Documentation from DigitalOcean explains A records directly map a domain to an IPv4 address. If the IP address of your server changes, you must update the A record manually. A records are suitable for scenarios where you have a static IP address and want direct control over the domain-to-IP mapping.

Documentation from Google Domains Help answers that a CNAME record maps an alias domain name to another (the canonical) domain name. This is useful for mapping multiple subdomains (like www, blog, shop) to a single website domain. If the target domain's IP address changes, the CNAME record automatically updates, ensuring the subdomain continues to point to the correct resource.