If you have ever looked through Google Domains Synthetic Records settings and noticed something called a Google Domains Synthetic Records, you may have wondered what it actually means. The term sounds technical, but the basic idea is much easier to understand than it first appears.
Google Domains synthetic records were special DNS-related settings that helped users configure common domain services without manually creating every individual DNS record. Instead of requiring users to understand every technical detail, Google Domains could generate the necessary DNS configuration behind the scenes.
This made tasks such as domain forwarding, email forwarding, and certain domain connections easier for people who were not familiar with DNS management.
There is one important detail to understand today: Google Domains Synthetic Records itself is no longer operating as a standalone domain registrar. Google completed the sale of its Google Domains assets to Squarespace in September 2023, and all Google Domains users were subsequently migrated to Squarespace. Google states that the migration of all domains was completed by July 10, 2024.
So, when people search for Google Domains synthetic records, they are often trying to understand an older Google Domains feature, troubleshoot a migrated domain, or understand DNS settings that were originally created through Google Domains.
ALSO READ: Dynamic Shared Object: A Simple Guide To What It Means
What Are Google Domains Synthetic Records?
A synthetic record was essentially a DNS configuration created automatically by Google Domains Synthetic Records to perform a particular function.
Traditional DNS records are usually added manually. For example, you might create an A record to point a domain toward a server or a CNAME record to connect a subdomain to another service.
Synthetic records worked differently.
Instead of asking users to manually enter every technical DNS value, Google Domains Synthetic Records could provide a simplified setting for a particular service. The system would then create or manage the underlying DNS configuration needed for that service.
Think of it like ordering a complete meal instead of buying every ingredient separately.
With a traditional DNS setup, you may need to understand several individual records. With a synthetic configuration, Google Domains Synthetic Records could handle much of that technical work for you.
This was particularly useful for people who wanted straightforward domain management without becoming DNS experts.
Why Did Google Domains Synthetic Records?
DNS can become complicated quickly.
A domain may need different records for a website, email, verification, forwarding, security, and other services. A small mistake can cause a website to stop loading or prevent email from reaching its destination.
Synthetic records helped simplify common tasks.
For example, a domain owner might want visitors who entered one domain address to automatically reach another website. Instead of manually working through several DNS settings, a built-in feature could handle the process.
The main advantages were:
- Easier configuration
- Less manual DNS work
- Fewer opportunities for simple configuration mistakes
- Convenient domain forwarding
- Easier email forwarding
- A more beginner-friendly domain management experience
This approach was especially useful for small website owners and people managing domains without technical backgrounds.
How Synthetic Records Were Different From Normal DNS Records
To understand synthetic records, it helps to understand ordinary DNS records first.
DNS stands for Domain Name System. Its job is to help translate human-readable domain names into information computers can use.
For example, when someone enters a domain name into a browser, DNS helps determine where that domain should go.
Common DNS records include:
A Records
An A record generally points a domain or hostname to an IPv4 address.
For example, a website might use an A record to point a domain toward its web server.
AAAA Records
An AAAA record performs a similar function but points to an IPv6 address.
CNAME Records
A CNAME record creates an alias from one hostname to another hostname.
This is frequently used for subdomains such as www.
MX Records
MX records tell mail systems where email for a domain should be delivered.
TXT Records
TXT records can contain information used for verification, email authentication, and other purposes.
These are conventional DNS records.
Synthetic records were more like a simplified service layer. Instead of requiring the user to manually configure all the underlying DNS details, Google Domains Synthetic Records could manage the configuration associated with a particular feature.
Google Domains Synthetic Records And Domain Forwarding
Domain forwarding was one of the most useful concepts associated with simplified domain management.
Imagine that you own:
example-old.com
but you want visitors to reach:
example-new.com
A forwarding service can redirect visitors from one address to another.
Google Domains Synthetic Records offered built-in forwarding functionality, which meant users didn’t necessarily have to configure a separate forwarding service themselves.
The important distinction is that forwarding and DNS are related, but they are not exactly the same thing.
DNS tells systems where a domain or hostname should resolve. A web redirect tells a browser to visit another address.
That difference becomes particularly important when troubleshooting migrated domains.
Google Domains Synthetic Records And Email Forwarding
Email forwarding was another useful feature.
Suppose you owned:
hello@example.com
and wanted messages sent there to arrive in an existing mailbox.
A forwarding system could help route those messages to another email address.
However, email depends heavily on DNS configuration, especially MX records. If those records are changed incorrectly, email delivery can stop working.
This is why domain owners should be careful when removing or replacing old DNS configurations.
After the Google Domains Synthetic Records migration, Squarespace specifically noted that some domain and email forwarding problems could occur when domains used custom nameservers alongside Google’s previous forwarding services. The recommended solution involved updating the DNS configuration appropriately.
What Happened To Google Domains?
This is one of the most important points for anyone researching Google Domains synthetic records today.
Google Domains was sold to Squarespace.
The transaction closed on September 7, 2023, transferring the Google Domains registrations and associated customer accounts to Squarespace.
By July 10, 2024, all Google Domains registrations had migrated to Squarespace.
That means you cannot manage a former Google Domains registration through the old Google Domains service in the way you could before the migration.
If you previously had a Google Domains account, your domain is now generally managed through Squarespace.
This is important because an older article or tutorial may refer to Google Domains menus and synthetic record options that no longer exist in the same form.
Why Are People Still Searching For Google Domains Synthetic Records?
There are several reasons.
First, many older websites and tutorials still discuss Google Domains features.
Second, domain owners may be troubleshooting DNS configurations created before the migration.
Third, developers and website administrators may encounter older documentation that uses the term “synthetic record.”
Finally, people may simply be trying to understand what happened to a DNS setting they remember seeing in Google Domains.
The term remains useful because it describes a real part of Google’s former domain-management system, even though the original Google Domains interface is no longer available.
Are Synthetic Records Still Used Today?
The answer depends on what you mean by synthetic records.
The specific Google Domains implementation should be considered a legacy concept because Google Domains registrations were moved to Squarespace.
Modern DNS management generally uses standard records such as A, AAAA, CNAME, MX, TXT, and related record types.
If you see DNS settings on a migrated domain, you should focus on what the current DNS provider requires rather than assuming that an old Google Domains synthetic-record setting can be recreated exactly.
This is particularly important when following older tutorials.
A guide written several years ago may tell you to click a Google Domains option that is no longer available. The underlying goal may still be achievable, but the steps and interface can be completely different.
What Should You Do If You Have An Old Synthetic Record?
Don’t delete an unfamiliar DNS configuration simply because it looks outdated.
DNS records can affect important services.
Before making changes, identify what the record was being used for.
Ask yourself:
- Is the domain connected to a website?
- Does the domain use custom email?
- Is email forwarding active?
- Is the domain forwarded to another website?
- Are verification records being used?
- Are third-party services connected to the domain?
- Are custom nameservers being used?
If everything is working correctly, unnecessary changes can create problems.
A good rule is simple: understand a DNS record before removing it.
If you are migrating services, document your existing settings first. Taking a screenshot or recording the existing DNS values can make troubleshooting much easier.
Common Problems After The Google Domains Migration
The migration from Google Domains to Squarespace was designed to preserve domain ownership and configuration as smoothly as possible, but certain services required attention.
One example was domain or email forwarding.
According to Squarespace’s current documentation, migrated Google Domains could experience forwarding problems when custom nameservers were involved with Google’s built-in forwarding services. In those situations, DNS records needed to be updated to restore forwarding.
Another important issue was Dynamic DNS.
Squarespace states that Dynamic DNS is not supported for migrated Google Domains. Existing DDNS records remain as A or AAAA records pointing to the last IP addresses supplied before migration, but they no longer update automatically.
This matters for users who previously relied on automatically updated IP addresses.
Synthetic Records vs. Custom DNS Records
It can help to think about the difference this way.
A custom DNS record is something you normally configure yourself.
A synthetic record was a Google Domains convenience feature designed around a specific function.
The first approach gives you more direct control.
The second approach gives you more convenience.
Neither approach is automatically better for every situation.
Beginners often benefit from simplified settings because there are fewer technical details to manage. Experienced users may prefer direct DNS control because they need precise configurations for websites, email systems, security tools, verification services, or specialized applications.
Why DNS Knowledge Still Matters
Even though domain platforms try to make DNS easier, understanding the basics can save you a lot of frustration.
You don’t need to become a networking expert.
You simply need to know what the most common records do.
An A record usually points a hostname to an IPv4 address.
An AAAA record points toward IPv6.
A CNAME creates a hostname alias.
An MX record controls mail delivery.
A TXT record can be used for verification and other text-based DNS information.
Once you understand these basic roles, DNS settings become much less intimidating.
How To Troubleshoot A Domain That Isn’t Working
When a domain suddenly stops working, don’t change everything at once.
Start with the basics.
Check the Domain Status
Make sure the domain is active and has not expired.
Check the Nameservers
Nameservers determine which DNS provider is responsible for answering DNS queries for the domain.
If your nameservers point somewhere unexpected, you may be editing DNS records in the wrong control panel.
Check the A and CNAME Records
If the website is not loading, verify that the records responsible for connecting the domain to the website are correct.
Check MX Records for Email Problems
If the website works but email does not, MX records deserve particular attention.
Don’t replace email records blindly. Your email provider may require specific values.
Check Recent Changes
DNS problems often appear immediately after a configuration change.
If something worked yesterday and stopped working today, look for recently modified records, nameservers, hosting settings, or forwarding rules.
Should You Recreate An Old Google Domains Synthetic Record?
Usually, the goal should not be to recreate the old record simply because it existed.
Instead, identify what the old configuration was supposed to accomplish.
For example, if the old synthetic record handled forwarding, determine how forwarding should be configured with your current provider.
If it was associated with email forwarding, determine which DNS and mail settings are required now.
If it was used for website connection, identify the current hosting provider’s required DNS records.
This approach is safer than trying to reproduce an old configuration without understanding its purpose.
What About Cloud Domains?
Google Cloud Domains is a related but distinct subject, which can cause confusion.
Google’s documentation explains that Cloud Domains continued as part of Google Cloud while domain registrations associated with Google Domains were transferred to Squarespace. Google Cloud also explains that domains using Google Domains DNS may need to move to Cloud DNS or another DNS provider if users need continued control over those DNS settings.
So, don’t automatically assume that Google Domains, Google Cloud Domains, Google Cloud DNS, and Squarespace Domains are all the same service.
They have different roles.
Understanding which service currently manages your domain is one of the first steps in solving a DNS problem.
Best Practices For Managing DNS Today
A few simple habits can prevent many DNS headaches.
Keep a Record of Important DNS Settings
Whenever your domain is working correctly, document the important records.
This gives you a reference point if something breaks later.
Don’t Delete Records Without Checking Them
An unfamiliar record may be connected to email, website hosting, verification, or another service.
Be Careful With Nameservers
Changing nameservers can effectively move DNS management from one provider to another.
That can affect your website, email, verification records, and other services.
Make One Change at a Time
If you change ten records simultaneously and something stops working, finding the cause becomes much harder.
Make a change, test it, and then continue.
Check Your Email Configuration
Website owners often focus on their homepage and forget that DNS also controls important email functions.
Always consider MX and related records before making major DNS changes.
Avoid Following Outdated Tutorials Blindly
This is particularly important with Google Domains.
Because Google Domains was migrated to Squarespace, older instructions may describe interfaces and options that no longer exist.
Google Domains Synthetic Records: The Main Takeaway
The easiest way to understand Google Domains synthetic records is to think of them as automated or simplified DNS configurations created to support particular domain services.
They helped make certain tasks easier by hiding some of the technical DNS work from users.
However, Google Domains is now a legacy service. Its domain registrations were acquired by Squarespace, and the migration has been completed.
That means the most useful question today isn’t simply, “Where is my Google Domains synthetic record?”
A better question is:
What was that record designed to do, and how should that function be configured with my current domain provider?
That shift in thinking makes DNS troubleshooting much easier.
Conclusion
Google Domains synthetic records were designed to make domain management simpler by automatically handling DNS configurations for certain services. For everyday users, this reduced the need to understand every technical DNS detail.
Today, however, Google Domains is no longer an active standalone registrar. Its domain registrations were transferred to Squarespace, so anyone managing a former Google Domains domain needs to work with the current domain-management system rather than relying on old Google Domains instructions.
The good news is that the underlying concepts are still easy to understand.
Learn what A, AAAA, CNAME, MX, and TXT records do. Understand the difference between DNS and forwarding. Check your nameservers before changing records. Most importantly, identify what an old configuration was actually doing before attempting to replace it.
Once you understand that purpose, the mystery surrounding Google Domains synthetic records becomes much smaller—and DNS management becomes far less intimidating.
FAQs
What is a Google Domains synthetic record?
A Google Domains synthetic record was a simplified DNS configuration that Google Domains created or managed automatically for certain domain services, such as forwarding.
Are Google Domains synthetic records still available?
Google Domains no longer operates as a standalone registrar. Its domain registrations were migrated to Squarespace, so the original Google Domains synthetic-record system is no longer managed through the old interface.
Can synthetic records affect my website?
Yes. Depending on what the configuration was used for, related DNS settings could affect website connections, forwarding, email, or other domain services.
What replaced Google Domains?
Squarespace acquired the Google Domains registrations and customer accounts. Former Google Domains users now manage their domains through Squarespace.
Should I delete an old synthetic record?
Not without understanding its purpose first. An old DNS-related configuration may still be connected to an important website, email, forwarding, or verification service.
ALSO READ: Context Match: A Simple Guide To Better Relevance
Elara Voss is a technology writer and immersive systems researcher at Argos.Vu, exploring the intersection of AI, virtual reality, and spatial computing. Her work focuses on how emerging technologies reshape the way we perceive, interact with, and understand information in the real world.
She writes about cutting-edge innovations, digital environments, and the future of human–technology interaction—translating complex ideas into engaging, forward-thinking insights.
