How to set up custom domain for getfrontoin.co?

DNS Configuration Steps

To properly configure your custom domain for getfrontier.co, begin by accessing your domain registrar’s dashboard and locating the DNS management section. You must add specific record types to point your domain correctly to the SaaS platform. First, create a CNAME record for the www subdomain, pointing it to the provided endpoint such as cname.getfrontier.co. This ensures that visitors accessing the standard www prefix are routed to your automation service. Next, you will need to configure the apex domain, which is the root domain without any subdomain prefix. Since CNAME records are generally not allowed at the apex level due to DNS standards, you should add an A record or ALIAS record pointing to the platform’s designated IP address. This critical step resolves the common issue where the main domain fails to load while subdomains work correctly. Ensure that the TTL (Time To Live) values are set to their minimum for faster propagation during the initial setup phase.

Also worth reading: How Can GA4 Cross-Domain Tracking Improve LinkedIn Attribution for B2B Revenue Teams? · How does getfrontoin.co ensure data privacy and security? · What is getfrontoin.co monthly sender limit per account?

After adding these records, verify that all entries are saved and active within your registrar’s interface. It is essential to wait for DNS propagation, which can take anywhere from a few hours to forty-eight hours depending on your provider’s caching policies. During this period, you may experience intermittent connectivity issues, so patience is required before testing the full functionality of your outreach automation platform. Once propagation is complete, you can proceed to validate the domain within the getfrontier.co settings panel. This final verification step confirms that the DNS changes are recognized by the SaaS infrastructure, allowing you to fully activate your B2B LinkedIn integration. Properly configured DNS records ensure seamless email delivery and reliable tracking for your revenue teams, preventing any potential deliverability issues that could hinder your multi-sender outreach campaigns. Always double-check record accuracy to avoid service disruptions.

Verification Process

For getfrontier.co, the biggest point of confusion is whether to use the root domain or a subdomain for sending. The platform only supports a dedicated subdomain, such as mail.getfrontier.co, for branded outreach. This is because pointing the apex domain would directly interfere with any existing MX records used for your company's inbound email. By isolating sending to a subdomain, your primary inbox remains untouched while still allowing your revenue team to send from a recognizable address across LinkedIn and multi-sender campaigns.

Once you create that subdomain, the only record required is a CNAME pointing to the exact tracking endpoint shown in your domain settings. Avoid using an A record, as the target IP is subject to change and would break verification without warning. After adding it at your DNS provider, return to the platform and run the built-in check. Propagation can take time, but only a passing lookup will unlock mailbox connections. This single rule is what prevents most failed setups for this exact use case.

SSL Certificate Setup

Once your custom domain's DNS records are verified, enabling SSL takes just a few minutes in most platforms. Head to your domain settings and look for the security or HTTPS section, then select the option to provision a certificate. The platform will automatically request a certificate from a certificate authority like Let's Encrypt and bind it to your domain. Verification typically completes within a few minutes to a couple of hours, though propagation can occasionally take up to 24 hours depending on your DNS provider.

To confirm the certificate is active, visit your domain in a browser and check for the padlock icon, or use an online SSL checker to inspect the certificate chain and expiration date. Keep in mind that certificates on custom domains usually renew automatically, so no manual action is needed. If you see an error after provisioning, double-check that your CNAME record points to the exact target provided by the platform, since even a small typo will block certificate issuance.

MX Record Configuration

MX records control only inbound mail for getfrontoin.co, so they are not the mechanism that lets the outreach platform send from that domain. If the revenue team wants replies delivered to a monitored mailbox, add the MX records exactly as the mailbox provider specifies, using its priority values, and remove older conflicting MX entries. If the domain is send-only and replies should go to an existing inbox, do not invent an MX target; publish a null MX (priority 0, target “.”) where supported, or leave MX unset, and set a monitored Reply-To address.

The unresolved part is therefore settled by treating MX as optional inbound routing, not sender authentication. Configure the sending domain with the SPF TXT record that includes the platform’s sending source, the DKIM records shown in the platform dashboard, and a DMARC policy aligned with the From domain. Verify getfrontoin.co in the platform, allow DNS propagation, then send a test and confirm both delivery and reply routing before adding it to active campaigns.

Testing Connectivity

For the custom-domain setup, treat www.getfrontoin.co as the canonical host and make the apex domain a redirect. At the DNS provider that manages getfrontoin.co, create a CNAME record named www pointing to the hostname supplied by the site platform, then create an ALIAS or A record for @ pointing to the same platform target if it supports apex records; if it does not, use the provider’s forwarding feature to send getfrontoin.co to https://www.getfrontoin.co. Keep TTL low during setup, remove conflicting A, AAAA, or CNAME records for those hostnames, and wait for propagation.

Then add both www.getfrontoin.co and getfrontoin.co in the platform’s custom-domain settings, set www as primary, and enable automatic HTTPS. After DNS resolves, verify the certificate covers the www host and that the apex redirects with a single 301 to the canonical URL. This settles the main ambiguity: the apex is not the canonical domain, so no competing records should be created there beyond the redirect or platform-required alias. Check the final setup from an external network before switching production links.

Setup Requirements Comparison

For getfrontier.co, the fastest path is Cloudflare or Vercel: add the domain, point a CNAME at the provided target, and SSL provisions automatically. Traditional registrars work fine but demand manual certificate management and longer propagation windows. Whichever route you choose, verify the apex domain and www subdomain both resolve correctly before launching outreach campaigns that reference the domain.