5/7/2023 0 Comments Dns tab for google domain![]() ![]() (If you want to be traditional, name it “dns.bind”) Then open that in your favorite text editor. ![]() Export this spreadsheet into a tab-separated values file. For the remaining cells, replace the TTL value with a corresponding number of seconds – e.g., change “1h” to 3600, “2w” to 1209600, and so on. Write down that common TTL value somewhere, then delete all cells whose TTL is equal to that. Almost all of the TTL’s you see are probably going to be identical. Then sort the entire sheet by name, subsorted by type, subsorted by TTL. Move the TTL column to the left of the Type column. Copy the “name”, “type” and “ttl” columns so they’re the same on each row. If you have a row where the “data” column has multiple lines, split that into N rows, with one line of data on each row. In a zone file, things have to be formatted asName(TTL)TypeData(TTL)TypeData(TTL)TypeDatawhere now the TTL is given as an integer number of seconds (and is skipped if it’s the same as the value set on the previous line), and the type has to be repeated on each line!So you need to go through this file and manually reformat it this way. The table you get on the web page has the formNameTypeTTLDataDataDataAnd the TTL is given as a string like “1h” or “2w”. Unfortunately, this table doesn’t look like a properly-formatted zone file. Then go to the “Synthetic Records” section above it, and for each section open the expando until you see a similarly-shaped table copy those rows into the sheet as well. There’s a table whose columns are name, type, TTL, and data: copy-paste it into your sheet. So open a new spreadsheet of your favorite sort, go to Google Domains, go to the domain whose DNS you want to move, and switch to the “Configure DNS” tab.Start with the “Custom Resource Records” section at the bottom. The easiest way to do this involves a spreadsheet. You’re going to have to convert a bunch of HTML tables from the Domains admin panel into a precise text format. Step 2: Copy a bunch of stuff into a spreadsheet. Pick a GCP project you’re going to use for DNS (or create a new one), then rungcloud dns managed-zones create -dns-name="." -description="A zone" "examplezonename"where you replace “” with your domain name (but keep that final trailing dot!), “examplezonename” with the name you want to give your zone, and the description with a description that’s meaningful to you. This is just the first step of the Cloud DNS migration instructions. The right way is to follow the Cloud DNS migration guide exactly-but the catch is that Google Domains doesn’t support exporting zone data! In this post we’ll lay out documentation (with some slightly janky copy-pasting), as it worked for the Humu team. What you need to do not only isn’t documented, but it’s super easy to mess up. The bad news is that Google Domains is missing a critical feature that lets you migrate things out of it easily. The good news is that Google Cloud DNS provides excellent instructions about how to migrate name service into it. ![]() Why we did this matters less than what happened when we did-and what we discovered in the process. We recently migrated Humu’s domain name services from Google Domains to Google Cloud DNS, because in our use case it’s more powerful, more flexible, and gives us service that wasn’t going to cut it with Google Domains. The goal of these posts is to help others avoid the same misery-and to make work better. This blog post is the first in an intermittent series about things we’ve learned in our first year as a startup. ![]()
0 Comments
Leave a Reply. |