GoDaddy DNS Management A Complete Guide to Editing Your DNS Records

GoDaddy hosts more domain names than any other registrar on the planet, which means millions of people end up managing their DNS through its control panel whether they planned to or not. The interface has changed several times over the years, the terminology can be inconsistent, and a single misconfigured record can take down your email, your website, or both. This guide covers every practical aspect of GoDaddy DNS management: where to find the settings, how to add or edit every major record type, what the common pitfalls are, how to verify your changes actually propagated, and how to avoid the mistakes that cause the most support tickets.

Where to Find DNS Settings in GoDaddy

GoDaddy has a habit of reorganizing its dashboard, so the path that worked six months ago may look different today. As of 2024, the reliable route is:

1. Log in at godaddy.com and click your account name in the top-right corner, then select My Products.
2. Find the domain you want to manage under the Domains section and click the three-dot menu beside it, then select Manage DNS. Alternatively, click the domain name itself and then choose DNS from the top navigation tabs.
3. You will land on the DNS Records page, which lists every record currently published for that domain.

If you purchased a hosting plan along with your domain, GoDaddy may have automatically populated your zone with A records pointing to its shared hosting servers and MX records pointing to Workspace Email. Always audit this list before you start editing so you know what is already there.

Understanding the DNS Records Panel

The panel shows each record's Type, Name, Value, and TTL (Time to Live). A few things trip people up immediately:

• Name field uses relative labels. For the root domain (example.com itself), enter @. For www.example.com, enter www. Do not type the full domain name — GoDaddy appends it automatically.
• TTL is in seconds. The default of 3600 means one hour. During a migration, drop this to 600 (ten minutes) a day in advance so propagation is faster when you flip the records.
• Multiple records of the same type can coexist for the same name (e.g., multiple MX records with different priorities), but only one A record per hostname is typically useful. GoDaddy will let you create duplicates — it will not warn you.

Adding and Editing Each Record Type

A Records (IPv4 Address)

An A record maps a hostname to an IPv4 address. To point your root domain to a web server at 203.0.113.45:

1. Click Add New Record.
2. Set Type to A, Name to @, Value to 203.0.113.45, TTL to 600.
3. Click Save.

If an existing A record points to GoDaddy's parked page or old hosting server, click the pencil icon beside it, update the Value field, and save. Do not create a second A record for @ — delete the old one first.

CNAME Records (Aliases)

A CNAME points one hostname to another hostname, not an IP address. Use this for subdomains like www, mail verification tokens, or third-party service verification. To make www an alias of your root domain:

• Type: CNAME
• Name: www
• Value: @

Critical rule: You cannot use a CNAME on the root domain (@). GoDaddy's panel will technically let you do this — the record will appear to save — but it will break your zone. Use an A record for @ and a CNAME only for subdomains.

MX Records (Mail)

MX records control where email for your domain is delivered. If you are moving from GoDaddy Workspace Email to Google Workspace, replace the existing MX records with Google's five servers:

Delete all existing MX records before adding the new ones. Leaving old MX records alongside new ones causes split mail delivery — some messages arrive, some bounce, and the problem is maddeningly inconsistent.

TXT Records (Verification and Email Authentication)

TXT records are the Swiss Army knife of DNS. You will use them for domain ownership verification (Google Search Console, Microsoft 365 setup), SPF, DKIM, and DMARC. To add an SPF record that authorizes Google Workspace:

One important GoDaddy-specific behavior: the panel automatically wraps TXT values in quotes when it saves them, so do not add your own quote marks in the Value field — you will end up with double-quoted values that some validators reject.

SRV Records

SRV records are needed for things like Microsoft Teams Direct Routing or Lync/Skype for Business. GoDaddy's SRV entry form has separate fields for Service, Protocol, Priority, Weight, Port, and Target. Fill each field independently rather than pasting a combined string — the panel does not parse combined formats correctly.

NS Records

You will rarely need to edit NS records directly. If you are delegating a subdomain to a different DNS provider (for example, pointing devops.example.com to Route 53 while keeping everything else on GoDaddy), you add NS records for the subdomain name pointing to the other provider's nameservers. Do not touch the root NS records — those define who is authoritative for your entire zone.

Changing Your Nameservers to an External Provider

If you want to manage DNS on Cloudflare, AWS Route 53, or another provider but keep your domain registered at GoDaddy, you need to change the nameservers rather than edit individual records in GoDaddy's panel. This is done in a completely different section:

1. Go to My Products, click the domain, then select the DNS tab.
2. Scroll to the Nameservers section at the bottom of the page.
3. Click Change, then choose I'll use my own nameservers.
4. Enter the nameservers provided by your external DNS host (e.g., ns1.cloudflare.com and ns2.cloudflare.com).
5. Save. GoDaddy will warn you that its DNS panel will no longer control your records — that is expected and correct.

Once nameservers are changed, any edits you make inside GoDaddy's DNS Records panel are completely ignored by the internet. Manage records exclusively in the new provider's dashboard. This is one of the most common sources of confusion: people change nameservers, then wonder why their GoDaddy record changes are not taking effect.

Common GoDaddy DNS Errors and How to Fix Them

Website Not Loading After Pointing A Record

If you updated your A record but the site still shows GoDaddy's parked page, there are three things to check:

• Old TTL still in effect. If the previous TTL was 3600, resolvers cached the old record for up to one hour. Flush your local DNS cache with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS, then test again.
• GoDaddy Website Builder or Hosting override. If you have an active GoDaddy hosting plan attached to the domain, it may override your A record. Go to the hosting plan settings and either disconnect the domain from the plan or cancel it.
• Forwarding rule still active. GoDaddy has a separate domain forwarding feature. If forwarding is enabled, it overrides your A record regardless of what the record says. Scroll to the Forwarding section in the DNS panel and remove any active forwarding rules.

Email Stopped Working After DNS Changes

The most frequent cause is accidental deletion of MX records or saving MX records without removing the old ones. Use the DNS Lookup tool to query your MX records directly and confirm the correct mail servers are listed. Also verify your SPF TXT record was not accidentally overwritten during an editing session — GoDaddy's panel occasionally clears unsaved fields when you navigate away.

DKIM Record Not Validating

DKIM TXT records contain long strings that GoDaddy's panel sometimes truncates. If your DKIM key is longer than 255 characters, it must be split into two quoted strings within the TXT value. The format looks like this:

GoDaddy's panel does not always handle this split gracefully through the UI. If the record fails validation even after saving, try removing it and re-entering just the raw string without outer quotes and see if the panel stores it correctly. If the problem persists, it is worth considering a move to Cloudflare DNS for that domain, which handles long TXT records reliably.

Changes Appear Saved But Do Not Propagate

This is almost always a nameserver mismatch. The domain's registrar nameservers in the WHOIS record do not match what GoDaddy's panel shows. This happens when a domain was transferred in from another registrar but the NS records were not updated at the registry. Run a WHOIS lookup on your domain and confirm the listed nameservers match what GoDaddy shows in its Nameservers section. If they differ, update them in the Nameservers section and allow 24 to 48 hours for the registry to propagate the NS delegation.

Lowering TTL Before a Migration

If you are planning to migrate your website or email to a new server, do this sequence at least 24 hours before the cutover:

1. Log into GoDaddy DNS and set the TTL on your A and MX records to 600 seconds.
2. Wait the current TTL duration (often one hour) so all resolvers have refreshed and are now caching the short TTL.
3. Perform the migration and update the record values on the cutover day.
4. Verify traffic is landing correctly on the new server.
5. Raise the TTL back to 3600 once you are confident the migration is stable.

Skipping step two is the classic mistake. If you set TTL to 600 at 9am and do the cutover at 9:05am, resolvers that cached the old record at 8:59am with the original 3600-second TTL will continue serving the old IP until 9:59am regardless of your TTL change.

Exporting Your GoDaddy DNS Zone

GoDaddy does not offer a native zone file export button in the standard interface. To get a copy of your zone records before migrating:

• Manually copy all records from the DNS panel into a spreadsheet or text file before making changes.
• Alternatively, use a command-line zone transfer if your account has Advanced DNS features enabled, or query each record type individually:

GoDaddy's default nameservers are ns1.domaincontrol.com and ns2.domaincontrol.com. Querying them directly bypasses any resolver caching and shows the authoritative current state of your zone.

Best Practices for Ongoing GoDaddy DNS Management

• Document every record before you edit it. Take a screenshot or paste the values into a notes file. GoDaddy does not maintain a visible change history in the standard interface.
• Use descriptive naming for subdomains. If you are adding a subdomain for a staging server, call it staging.yourdomain.com with a dedicated A record so it is easy to identify and remove later.
• Do not use GoDaddy's default TTL of 3600 for records that change frequently. For dynamic IPs or cloud workloads that scale in and out, use 300 seconds.
• Separate registrar from DNS provider. Keeping your domain registered at GoDaddy while managing DNS at Cloudflare gives you better performance (Cloudflare's anycast network is faster), a more reliable interface, and free DNSSEC. The nameserver change takes five minutes.
• Enable two-factor authentication on your GoDaddy account. DNS hijacking via compromised registrar accounts is a real and documented attack vector. An attacker who controls your GoDaddy login can redirect your entire domain to a phishing site in under two minutes.

Verifying Your Changes

After saving any record in GoDaddy, always verify it from outside your network. Your local resolver and browser cache can mask problems for hours. The fastest verification approach:

Querying Google's public resolver (8.8.8.8) gives you a real-world view from outside your ISP's caching infrastructure. If the record appears correctly there, it is live for most users. If it does not appear yet, check the TTL on the old record — that is your maximum wait time.

GoDaddy DNS management is not complicated once you understand where the controls are and what each record type does. The errors that cause the most downtime are almost never complex DNS problems — they are simple oversights: forgetting to delete old records, misunderstanding what the @ symbol means, or not accounting for existing TTL before a migration. Take a methodical approach, verify every change, and your zone will stay clean and stable.