Managing Custom DNS and Subnet Policies on GoDaddy Domains

Managing your domain's network architecture requires precise coordination between your public-facing name resolution and private infrastructure routing. GoDaddy custom DNS subnet management combines the control of your authoritative domain records with the mathematical requirements of IP address allocation. Whether you are assigning static public IP addresses to your web servers or mapping internal network boundaries for remote branch offices, getting these configurations right ensures your services remain accessible and secure.

To properly allocate and verify the IP blocks you plan to assign to your custom DNS records, using a reliable planning utility is essential. You can map out your network ranges efficiently using the Subnet Calculator to determine exact usable host ranges, broadcast addresses, and netmasks before making any changes in your provider dashboard.

Understanding Custom DNS and Subnet Fundamentals

Custom DNS management on standard domain registrars involves creating authoritative mappings between human-readable domain names and machine-readable IP addresses. When a client queries your domain, your DNS provider returns the IP address associated with that record, directing traffic to your infrastructure.

Subnet management, on the other hand, deals with how your organization divides its assigned IP address space into smaller, manageable network segments. When working with custom DNS records, understanding subnets helps you properly map multi-region deployments, load balancers, and internal services.

IPv4 vs. IPv6 Addressing in GoDaddy

When configuring records in your management console, you will primarily work with two IP versions:

• IPv4 (A Records): 32-bit numerical addresses expressed in four octets (e.g., 192.0.2.1). Most legacy and standard applications rely on IPv4.
• IPv6 (AAAA Records): 128-bit addresses expressed in hexadecimal groups (e.g., 2001:db8::1). Modern infrastructure and mobile networks increasingly depend on IPv6.

The Role of CIDR Notation

Classless Inter-Domain Routing (CIDR) notation defines your network prefix and subnet mask (e.g., 192.0.2.0/24). While DNS records point to individual host IPs rather than entire subnets, your subnet policies dictate which hosts are eligible to receive public traffic through those DNS entries.

Step-by-Step: Configuring Custom DNS Records on GoDaddy

Updating your domain records requires access to your primary domain portfolio management screen. While exact interface layouts change periodically, the core navigation paths remain consistent.

1. Log into your account and navigate to your domain portfolio dashboard.
2. Locate your target domain, open its action menu, and select the option to manage DNS or view DNS records.
3. Review your existing zone file. Look for conflicting A, AAAA, or CNAME entries that might overlap with your intended subnet deployment.
4. Click the button to add a new record.
5. Select the record type (A for IPv4 or AAAA for IPv6).
6. Enter your host identifier (e.g., @ for the root domain or a subdomain like shop).
7. Input the specific target IP address belonging to your allocated subnet range.
8. Set an appropriate Time to Live (TTL). A standard TTL of 1 hour (3600 seconds) works well for stable environments, while 600 seconds or lower is recommended during planned migrations.
9. Save your changes.

Sample Record Configuration Table

Record Type	Host / Name	Value / Points To	TTL	Description
A	@	192.0.2.10	1 Hour	Root domain pointing to primary web server
A	www	192.0.2.10	1 Hour	WWW subdomain alias pointing to primary web server
A	mail	192.0.2.50	1 Hour	Mail server entry within dedicated mail subnet
AAAA	@	2001:db8::10	1 Hour	IPv6 root domain binding

Verifying DNS and Subnet Mappings via Command Line

Once you have updated your zone file, you must verify that global name servers are reflecting your changes accurately. Using command-line tools allows you to bypass local caching issues.

Using nslookup

Run a basic query to check your newly updated A record:

nslookup example.com

Sample output:

Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	example.com
Address: 192.0.2.10

Using dig for Detailed Diagnostics

For advanced checks including TTL values and authoritative name server responses, use dig:

dig example.com +noall +answer

Sample output:

example.com.		3600	IN	A	192.0.2.10

Verifying Connectivity with curl

Confirm that the server at your target IP address is responding to web requests:

curl -I https://example.com

Best Practices for Subnet and DNS Alignment

Maintaining clean network policies prevents downtime and simplifies security auditing.

• Match TTLs During Migrations: Lower your TTL values at least 24 hours before shifting traffic to a new subnet range.
• Document Subnet Allocations: Keep an internal register mapping every active public IP address in your DNS zone to its specific server role and physical or cloud data center.
• Implement Split-Horizon DNS Carefully: If you run internal subnets that mirror public domains, ensure your internal resolvers have proper forwarding rules to prevent routing loops.
• Audit Unused Records: Periodically clean up dangling CNAME and A records pointing to decommissioned subnet ranges to mitigate subdomain takeover vulnerabilities.

Common Mistakes and How to Fix Them

Even experienced engineers encounter configuration pitfalls when merging DNS management with subnet routing.

• Mistake 1: Pointing DNS to a Subnet Network Address. Pointing an A record to a network ID (e.g., 192.0.2.0) or broadcast address (192.0.2.255) instead of a specific host IP will cause connection failures.
  • Fix: Use the specific usable host IP from your subnet calculation (e.g., 192.0.2.1).
• Mistake 2: Conflicting CNAME and A Records. Attempting to create a CNAME record for a root domain (apex) or creating a CNAME that conflicts with an existing A record.
  • Fix: Use A/AAAA records for root domains and reserve CNAMEs strictly for subdomains.
• Mistake 3: Forgetting IPv6 AAAA Records. Configuring only IPv4 A records while modern clients attempt IPv6 lookups, resulting in slow connection fallbacks.
  • Fix: Always pair IPv4 updates with corresponding IPv6 records when your infrastructure supports dual-stack networking.

Quick Configuration Checklist

• Calculated exact host and subnet boundaries using an IP planning tool.
• Logged into your domain portfolio dashboard and located zone file settings.
• Created or updated A and AAAA records pointing to valid host IPs.
• Verified propagation globally using dig or nslookup from multiple networks.
• Tested live web or service connectivity using curl or browser checks.