Google Domains Synthetic Records: The Complete Guide

If you managed a website, connected a custom domain, or set up a professional email address over the past decade, chances are you used Google Domains at some point. Known for its clean interface, affordable pricing, and beginner-friendly tools, Google Domains stood out from many traditional registrars. One of its most useful features was Google Domains synthetic records, a built-in DNS capability that simplified tasks like Google Domains email forwarding, subdomain aliases, and Google Domains port forwarding without requiring complex manual DNS configurations. These synthetic records Google Domains users relied on made managing domains faster and more accessible, especially for small businesses and website owners. However, following the Google Domains migration to Squarespace, many of these familiar tools changed or disappeared, leaving users wondering how to replace them. In this guide, we’ll explain Google Domains DNS synthetic records, how they worked, their role in Google Domains DNS records setup, and what you should know about these Google Domains legacy DNS features if you’re now managing your domain through Squarespace.

What Were Google Domains Synthetic Records?

To understand synthetic records, it helps to first understand a basic frustration that many non-technical website owners faced. Setting up a domain properly usually meant creating several individual DNS records by hand, things like A records, CNAME records, MX records, and TXT records, each with its own syntax and its own room for error. One small typo could break an entire website or email setup.

Synthetic records google domains style were essentially bundled, pre-configured shortcuts that automated this manual process. Instead of asking users to understand the difference between an A record and a CNAME record, Google Domains let you pick a goal, like forwarding a subdomain or connecting to Google Workspace, and it would generate and manage the correct combination of underlying DNS records for you. In short, a synthetic record was not a new type of DNS record recognized by internet standards. It was a Google-specific abstraction layer that sat on top of standard DNS and quietly did the technical work behind the scenes.

The Three Main Types of Synthetic Records

Google Domains offered three primary categories of synthetic records, and each one served a distinct purpose for site owners. Below is a table summarizing what each type did and who typically used it.

Subdomain forwarding was probably the most commonly used feature since it let users set up a google domains custom redirect without touching a single manual DNS entry. Dynamic DNS, on the other hand, appealed heavily to hobbyists and small business owners running personal servers from home, since home internet connections usually have IP addresses that change periodically. The Google Workspace record simplified what used to be a multi step process into something that took only a couple of clicks.

How Google Domains DNS Synthetic Records Worked in Practice

The actual mechanics behind google domains dns synthetic records were relatively simple from the user’s side, even though a fair amount of infrastructure was working in the background. When you created a synthetic record for subdomain forwarding, for example, Google Domains would automatically generate the necessary A and CNAME records pointing to Google’s own forwarding servers. Those servers then handled the actual redirect and, in many cases, provisioned a free SSL certificate so the forwarded domain would work correctly over HTTPS.

For google domains email forwarding, users could redirect incoming mail sent to their custom domain toward an existing inbox like Gmail, without needing to set up a full mail server. This was extremely popular among freelancers, small business owners, and bloggers who wanted a professional looking email address without the cost of a dedicated email hosting plan.

For google domains port forwarding style setups, particularly through Dynamic DNS, users would install a small client on their home network, such as ddclient, and configure it with credentials provided by Google Domains. That client would periodically check the home network’s public IP address and notify Google Domains whenever it changed, keeping the DNS record accurate at all times. This made it possible to reliably reach a home server, security camera system, or personal cloud setup using a friendly domain name instead of memorizing a constantly shifting IP address.

Why Synthetic Records Became So Popular

The appeal of synthetic records mostly came down to accessibility. DNS management has traditionally been intimidating for non technical users, and a single misconfigured record can take an entire website or email system offline. By packaging these common configurations into a guided, point and click experience, Google Domains removed a significant barrier for beginners while still giving experienced users the flexibility to configure standard DNS records manually if they preferred.

This approach also reduced the volume of support requests Google had to handle, since fewer users were making manual mistakes. For small business owners in particular, the combination of an affordable registrar, clean interface, and features like the Google Workspace synthetic record made Google Domains an attractive one-stop option for getting a business online quickly.

Advantages and Disadvantages of Using Synthetic Records

Like any simplified tool, synthetic records came with real benefits as well as some limitations. The table below breaks down both sides fairly.

This table highlights an important theme that runs through the rest of this article. While synthetic records were genuinely useful, their biggest drawback turned out to be their dependency on Google’s own ecosystem, something that became very relevant once Google decided to exit the domain registrar business altogether.

The Google Domains Migration to Squarespace

In 2023, Google announced it was selling the Google Domains business to Squarespace. This was a significant shift for millions of domain owners who had grown used to Google’s simple interface and synthetic record features. The google domains migration to Squarespace took place gradually, with domains being transferred in batches rather than all at once, and the process was fully completed in mid 2024.

According to Squarespace’s own support documentation, once a domain finished migrating, several of the more advanced Google-specific features stopped functioning the way they used to. Squarespace states that it supports the core DNS record types, custom nameservers, domain forwarding, email forwarding, DNSSEC, and glue records, aiming to preserve as much continuity as possible for migrated users. That said, Squarespace has also been upfront that a handful of advanced features simply did not carry over, most notably Dynamic DNS and the ACME DNS API used for automated SSL certificate renewal.

This means that anyone who relied specifically on the Dynamic DNS synthetic record for a home server or remote access setup needed to find an alternative solution once their domain moved over to Squarespace. Google’s own documentation on the migration explains that any active Dynamic DNS records are essentially frozen in place after the transition, converted into static A or AAAA records that point to the last known IP address, with no further automatic updates. In other words, the underlying record does not disappear, but it stops doing the one thing that made it useful in the first place, which was updating itself.

Google Domains Legacy DNS Features and What Changed

For users who are still getting used to their migrated accounts, understanding google domains legacy dns features is essential to avoid confusion. Static DNS records, domain forwarding, and email forwarding generally continued working using the last configuration that was active before migration, but users lost the ability to make live changes to those settings through the old Google interface. Any updates now have to be made directly within the Squarespace dashboard instead.

It is worth noting that if your domain is still pointed at Google’s original DNS infrastructure rather than fully transitioned into Squarespace’s DNS management, you may find that you are unable to edit those records at all until you either switch to Squarespace’s nameservers or move to an entirely different DNS provider. This has caught some site owners off guard, especially those who had not logged into their domain settings in a long time and assumed everything would continue exactly as before.

How to Set Up Synthetic Records Today

Since Google Domains no longer accepts new registrations and all existing domains have completed their migration, the honest answer to how to setup synthetic records today is that you technically cannot, at least not in the original Google Domains sense. That specific feature set was tied directly to Google’s own infrastructure and has not been replicated identically by Squarespace or any other registrar.

That said, the underlying goals that synthetic records were designed to solve, like domain forwarding, email forwarding, and dynamic IP tracking, are still achievable using other tools. Domain forwarding and email forwarding can be configured manually through Squarespace’s domain management panel, or through the DNS settings of any other registrar you choose to move your domain to. For Dynamic DNS specifically, many users have turned to third party services like Cloudflare or dedicated DDNS providers, which offer similar automated IP tracking capabilities, though the setup process requires a few more manual steps than the original one-click Google experience.

Do’s and Don’ts for Managing Your Migrated Domain

If your domain has already moved from Google Domains to Squarespace, or if you are considering switching registrars entirely, here are some practical do’s and don’ts to keep your website and email running smoothly.

Taking a few minutes to audit your domain settings can save you from unexpected downtime, especially if your website or email setup has been running quietly in the background for years without much attention.

Should You Stick with Squarespace or Move Elsewhere?

This is a question a lot of former Google Domains users have been asking themselves. Squarespace has made a genuine effort to preserve continuity, and for the vast majority of standard use cases, like a simple website, a redirected domain, or business email through Google Workspace, the transition has been relatively smooth. Squarespace has also stated that it is investing in improving its domains platform going forward.

However, if your setup depended heavily on Dynamic DNS or other Google-specific synthetic record features, you may find that Squarespace’s current offering does not fully match your needs. In that case, transferring your domain to a registrar that specializes in advanced DNS configuration, such as Cloudflare, may be a better long-term fit. Migrating a domain is not overly complicated, but it does require some planning, particularly around making sure your existing DNS records are properly recreated at the new provider before you switch nameservers, to avoid any downtime for your website or email.

For anyone wanting to review the most accurate, up to date details about what changed during this transition, Squarespace’s official help center article on the migration is a reliable resource and can be found at https://support.squarespace.com/hc/en-us/articles/17131164996365-About-the-Google-Domains-migration-to-Squarespace.

Final Thoughts on Google Domains Synthetic Records

Google domains synthetic records were a genuinely thoughtful solution to a common problem, making DNS management approachable for people who had no interest in learning the technical details behind A records and CNAME entries. For years, they made it easy for beginners to launch a website, redirect a domain, set up business email, or run a personal home server without a steep learning curve.

With Google Domains now fully retired and folded into Squarespace, that specific feature set no longer exists in its original form. Static forwarding and email forwarding have largely carried over in a usable state, but Dynamic DNS support has been dropped entirely, leaving affected users to seek out alternative tools. If you are still managing a domain that made this transition, it is worth taking the time to review your current settings, confirm everything is routing correctly, and put a plan in place for any features that no longer work the way they used to. A little bit of proactive checking now can prevent a much bigger headache down the road.