Google Domains Synthetic Records were built to save you from hand typing boring DNS records. They acted like smart shortcuts. You clicked one option, filled in a small form, and Google created the needed DNS setup in the background.
TLDR: Synthetic Records were automation buttons for DNS chores, such as web forwarding, email forwarding, and Google service setup. For example, instead of adding 5 separate mail records by hand, a small business could click one Google Workspace option and finish in about 2 minutes. In a 20 domain portfolio, that could cut setup time by 70% or more. The records looked fancy in the panel, but under the hood they often turned into plain DNS records like MX, CNAME, TXT, and A records.
What Were Synthetic Records?
A Synthetic Record was not a special record type used by the whole internet.
That part confuses people.
DNS itself has common record types. Think of:
- A records for pointing a name to an IPv4 address.
- AAAA records for pointing a name to an IPv6 address.
- CNAME records for aliasing one name to another name.
- MX records for mail servers.
- TXT records for verification, SPF, DKIM, and other text data.
A Synthetic Record sat above those. It was a Google Domains feature in the control panel. It grouped a task into one neat button.
So instead of saying, “Please create two MX records, one TXT record, and maybe verify this domain,” the panel said something friendlier. Something like set up email or forward this domain.
That was the whole trick.
Less typing. Fewer mistakes. Faster setup.
Why Google Built Them
DNS is powerful. It is also annoying.
One wrong dot can break a site. One missing mail record can make messages vanish. One bad verification record can leave you staring at a “not found” warning for an hour.
Honestly, it feels like DNS was designed by people who enjoy tiny boxes and scary labels.
Google Domains tried to soften that pain. Synthetic Records were made for normal domain owners, not only network admins.
They helped with common jobs:
- Forwarding a domain to another website.
- Forwarding a subdomain, such as shop.example.com.
- Forwarding email from one address to another inbox.
- Connecting Google Workspace with fewer manual records.
- Connecting selected Google services that needed DNS proof.
- Updating DNS when a home server address changed, through Google’s supported update method.
The goal was clear. Make DNS feel less like wiring a spaceship.
What They Did Behind the Curtain
Imagine you want www.example.com to point to your website host.
The manual way works like this:
- Open DNS settings.
- Pick a record type.
- Enter the host name.
- Enter the target.
- Set the TTL.
- Save it.
- Wait.
- Hope nothing was typed wrong.
A Synthetic Record skipped much of that.
You picked the task. Google filled in the record pattern. Then it pushed the result into its DNS system.
For web forwarding, Google might not create one simple public DNS record that explains everything. It could also connect your domain to Google’s forwarding service. That service then sent visitors to the final address.
For email forwarding, the panel could hide the ugly bits. You asked for hello@example.com to forward to your Gmail inbox. Google handled the service link and supporting DNS setup.
For Google Workspace, it could prepare the needed mail routing records. That meant fewer trips to help docs. Fewer copy and paste errors. Fewer “why is my email broken?” moments.
How DNS Record Automation Works
DNS automation is simple in theory.
The software asks what you want. Then it writes the DNS records for you.
Here is the usual flow:
- You choose a goal. Example: send mail to Google Workspace.
- The tool checks your domain. It confirms the zone exists and can be edited.
- The tool builds records. It creates names, values, priorities, and TTLs.
- The tool checks for conflicts. It may warn you if another mail setup already exists.
- The tool saves the records. The DNS provider publishes them.
- DNS resolvers refresh. This can take minutes, or longer if old records were cached.
That is it.
No wizardry. Just good form design and safe record writing.
The best systems also validate input. They reject spaces in the wrong places. They stop duplicate records. They remind you when a root domain cannot use a CNAME in many DNS setups.
That matters. A simple typo can cost real money. If checkout traffic goes to the wrong place for 30 minutes, the damage is not theoretical.
A Simple Example
Say Mia owns a bakery.
Her domain is miabakes.com. Her online ordering page lives on another service at orders.examplecart.com/miabakes.
Mia wants order.miabakes.com to send visitors there.
Without automation, she may need to read support docs. Then she adds a CNAME. Or maybe she uses forwarding. Or maybe the cart service asks for a TXT record too.
Expect to waste time on tiny choices like “host” versus “name.” Some panels use one word. Some use the other. Great. Very helpful.
With a Synthetic Record style tool, Mia picks subdomain forwarding. She enters:
- Subdomain: order
- Destination: https://orders.examplecart.com/miabakes
- Redirect type: temporary or permanent
Then she saves.
The tool handles the rest.
That is the charm. Mia keeps selling cupcakes. DNS stays in its little cave.
Synthetic Records Were Helpful, But Not Perfect
They made easy tasks easier. Still, they had limits.
First, they could hide details too well. If something broke, users did not always know which real records were involved.
Second, synthetic setups were tied to the provider’s panel. If you moved DNS elsewhere, the shortcut did not always move with you. The regular records might need to be recreated by hand.
Third, forwarding is not the same as hosting. A forwarded domain sends users to another address. It does not store your website files.
Fourth, email forwarding is not full email hosting. It can receive and pass along mail. It may not give you a full mailbox, calendar, or sending setup.
This is where people get burned. The button sounds bigger than it is.
What Happened After Google Domains
Google Domains is no longer sold as a Google registrar product. Domain registrations were moved to Squarespace Domains after the sale of the service.
Still, the idea lives on.
Many DNS providers now use guided setup. They call it different things. The idea is the same.
Click a service. Confirm the domain. Let the platform create the records.
You see this with website builders, email hosts, security tools, newsletter platforms, and shop systems.
They all want fewer support tickets. Users want fewer broken domains. Everyone wins, at least most of the time.
Common Tasks Automation Can Handle
Modern DNS automation can help with:
- Domain verification using TXT records.
- Email routing using MX records.
- Spam protection using SPF, DKIM, and DMARC records.
- Website connection using A, AAAA, or CNAME records.
- Subdomain setup for shops, blogs, apps, and help centers.
- Certificate checks for SSL setup.
Good automation also shows a preview. That is a nice touch. Users should be able to see what records will be added before they click save.
Best Practices Before You Click
Automation is useful. Blind clicking is not.
Before using a one click DNS setup, do this:
- Check existing records. Do not overwrite working mail or site records by accident.
- Take a screenshot. It gives you a quick rollback reference.
- Read the target value. Make sure it matches the service you trust.
- Use lower TTLs before big moves. This can reduce waiting time.
- Test after saving. Try the site, email, and verification page.
If a tool says it will “fix everything,” be skeptical. DNS is not one thing. It is a stack of small instructions. Each one has a job.
The Big Idea
Synthetic Records were designed to turn common DNS chores into friendly actions.
They did not replace DNS. They wrapped it.
That wrapper mattered. It helped people forward domains, connect email, and set up services without learning every record type on day one.
DNS record automation still works the same way. The tool turns your goal into records. Then it publishes them. Then the internet catches up.
The simple rule: automation is great for speed, but you should still know what it changed.
That tiny bit of knowledge can save your site, your email, and your afternoon.
