How to Manage DNS Zones on HostGator

DNS is the system that connects a domain name with the online services behind it. When someone types a web address into a browser, DNS helps locate the correct hosting server, mail platform, verification service or other destination. Managing a DNS zone means maintaining the collection of records that controls these connections.

HostGator customers commonly use DNS settings when launching a website, connecting a domain purchased elsewhere, setting up professional email or verifying a service such as Google Workspace. A small mistake can send visitors to the wrong server or stop email from arriving, so each change deserves a careful approach.

The exact screen can vary according to your HostGator plan, domain registration arrangement and account interface. In most cases, the relevant tools are available through the customer portal, cPanel or a domain management area. You may also find useful walkthroughs in HostGator’s knowledge base and video tutorial library.

Australian businesses have a few local details to keep in mind. A .com.au domain normally has eligibility requirements managed under auDA, Australian providers often display prices in Australian dollars including GST, and DNS timing can be confusing when checking changes from Sydney, Perth or Melbourne networks. The principles remain the same, but local registration and support arrangements can affect the process.

Record type Main purpose Typical value or destination Common warning
A Sends a name to an IPv4 address HostGator server IP Use the correct current IP
AAAA Sends a name to an IPv6 address IPv6 server address An old value can cause inconsistent access
CNAME Points one hostname to another hostname www to the root domain Do not use a CNAME at the root in most setups
MX Directs email delivery Mail provider hostname Priority values matter
TXT Stores verification or policy text SPF, DKIM or verification string Copy every character accurately
NS Identifies authoritative DNS servers Nameserver hostnames Changing these moves DNS control

Understanding The DNS Zone

A DNS zone is the administrative set of records for a domain or subdomain. It can include the root domain, commonly written as example.com, along with hostnames such as www.example.com, mail.example.com or shop.example.com. The zone does not contain website files; it tells internet services where those files and related services can be found.

The most familiar record is the A record, which connects a hostname to an IPv4 address. An AAAA record performs a similar job for IPv6. A CNAME creates an alias between hostnames, while MX records identify the servers responsible for receiving email. TXT records are frequently used for domain verification, SPF email authorisation and other security policies.

Nameservers are slightly different. They tell the internet which DNS system holds the authoritative zone. If your domain uses HostGator nameservers, you generally manage its records in HostGator or cPanel. If it uses nameservers from another provider, editing HostGator’s zone may have no effect because the public internet is consulting the other provider instead.

Finding The HostGator DNS Tools

Sign in through the HostGator customer portal and open the relevant hosting package or domain. Depending on the account layout, look for cPanel, Domains, Zone Editor or a similar DNS management option. Shared hosting customers will often find Zone Editor inside cPanel, where domains and subdomains can be selected before records are created or changed.

Before editing anything, confirm the domain name and the active hosting package. Accounts with several projects can contain staging domains, addon domains and parked domains, making it easy to modify the wrong zone. Check the spelling carefully, especially where a brand has both a .com and a .com.au version.

If the editor is not visible, the domain may be using external nameservers, the plan may have a different management arrangement, or the account may require support assistance. HostGator’s ticket system can confirm where DNS authority sits. Avoid repeatedly changing settings simply because the expected result has not appeared yet; propagation can take time.

Choosing The Correct Record

Use an A record when a domain or subdomain must reach a fixed IPv4 address. For example, example.com and www.example.com might point to a HostGator server, although www is often configured as a CNAME to the root domain. If your provider gives you an IPv6 address, an AAAA record may be required as well.

CNAME records are useful for services that provide a hostname instead of an IP address. A marketing platform, ecommerce tool or external landing-page provider may ask you to point offers.example.com to a supplied destination. Follow that provider’s instructions exactly, including whether the final dot is shown in the hostname.

Email requires special care. MX records determine where messages are delivered, and the lowest priority number is normally tried first. If you move from HostGator email to another provider, remove obsolete MX records when instructed and add the new provider’s complete set. TXT records can support SPF, DKIM and DMARC, but these policies need to match your actual mail service.

A business publishing a niche website, for instance, might add a subdomain for an external resource such as a real-money slots guide. The content itself does not determine the DNS method; the external platform’s instructions do. Never guess an IP address or replace a requested CNAME with an A record simply because both appear to point somewhere.

Adding And Editing Records Safely

In Zone Editor, select the domain and choose the option to add a record. Pick the record type, enter the name, provide the destination, and set the TTL if the interface offers that field. For the root domain, the name may appear as @, the full domain or a blank field. HostGator’s labels can vary, so use the on-screen explanation rather than entering @ automatically.

TTL means time to live, or how long DNS resolvers may cache a response. A shorter TTL can help during a planned migration, while a longer value can reduce repeated lookups after the configuration is stable. Changing TTL does not instantly clear caches that were already stored under an earlier value.

Export or record the existing values before making changes. A screenshot, text file or carefully prepared change log can help you restore a working configuration. When editing an existing record, change one relevant value at a time and save it before testing. Keep the old value available until the new service is confirmed.

Do not create duplicate records without understanding the effect. Two A records may deliberately distribute traffic, but an accidental second MX or conflicting TXT record can cause unreliable mail delivery or failed verification. Some services require several TXT strings, so preserve each separate entry instead of combining them unless the instructions explicitly say to do so.

Connecting A Domain Or Transfer

When a domain is registered with another company but hosted at HostGator, you can usually connect it by updating nameservers at the registrar or by adjusting individual DNS records. Changing nameservers gives HostGator control of the full zone. Editing individual records keeps DNS with the existing provider and sends only selected traffic to HostGator.

A full domain transfer is a separate process from changing DNS. It may involve unlocking the domain, obtaining an authorisation code, checking contact details and approving transfer emails. Australian .au domains follow local registry rules, and transfer eligibility or registrant information may need attention before the move can proceed. Read the transfer requirements before changing nameservers.

For a practical overview of the wider process, review this guide to transferring a domain. The important distinction is that a transfer changes the registrar relationship, whereas nameserver changes alter where DNS is managed. Either action can affect email and verification records if the existing zone is not reproduced correctly.

Before moving nameservers, copy all important records from the current provider: A, AAAA, CNAME, MX, TXT, SRV and any custom records. Recreate them in HostGator’s zone first where possible, then change the nameservers. This reduces the chance that a live website works while email or a connected application quietly stops.

Checking Propagation And Fixing Problems

DNS updates do not arrive everywhere at the same moment. A resolver in Brisbane may show the new value before one in Adelaide, while a mobile connection or office network may retain an older response. Australian users may also be checking through different providers, including NBN services, mobile networks and business DNS filters.

Allow the stated TTL and some additional time before deciding that a change failed. Use several independent DNS checking services, test from a private browser window and compare results on a mobile connection. For website changes, test both the root domain and www; for email, send messages in both directions and check whether the correct mailbox receives them.

Common problems include an incorrect IP address, a CNAME pointing to the wrong hostname, an old MX record left in place, or DNS being managed somewhere other than HostGator. A missing trailing dot is usually handled by the interface, but an incorrectly entered full hostname can create an unintended subdomain. Look for duplicate or contradictory entries before contacting support.

DNSSEC can add another layer of protection against forged DNS responses, but it must be configured consistently between the registrar and DNS provider. If DNSSEC records remain at the registrar after nameservers change, the domain may become unreachable. Treat DNSSEC as a planned configuration rather than enabling it casually during a migration.

Protecting Access And DNS Records

DNS management is part of your site’s security. Use a strong, unique HostGator password, enable available multi-factor authentication, and limit account access to people who genuinely need it. A compromised hosting account can allow an attacker to redirect the website, intercept email or add misleading verification records.

Keep recovery details current and store important DNS information somewhere protected. A secure internal reference, such as documented account safes, can hold registrar details, server addresses and change records when handled according to your organisation’s security policy. Do not place passwords or authorisation codes in a public document or shared chat.

Review the zone after completing a migration or adding a new service. Remove records for cancelled platforms, old verification tokens and unused subdomains when appropriate. Retaining every historical entry can create confusion and may leave forgotten services discoverable.

Practical DNS Management Habits

A simple operating routine prevents many outages. Before any change, identify who currently controls the nameservers, what service the record supports and how the result will be tested. Record the date, old value, new value and person responsible, which is especially useful for a small team working across AEST and AEDT.

Knowing When To Contact Support

HostGator support is appropriate when the zone editor is unavailable, the domain appears in the wrong account, or the active nameservers cannot be identified. It is also useful when a change remains incorrect after caches should have expired. Provide the domain, record type, old and new values, time of the change and the result of your testing.

Avoid sending account passwords or full authorisation codes in a support ticket. A clear description is usually enough for support staff to investigate, and screenshots should be checked for exposed private information first. If the issue affects email, mention the sending and receiving addresses, bounce message and approximate time.

For Australian customers, support timing may not match local business hours. A website owner in Perth can experience a different support overlap from someone in Sydney, particularly around daylight-saving changes. Record the issue precisely so it can be handled efficiently rather than relying on an informal “it’s not working” report.

The key distinction to remember is that DNS records direct individual services, while nameservers determine which provider controls the zone. Check that authority first, make measured changes, preserve the old configuration and allow time for propagation. Good DNS management is careful record-keeping as much as it is technical editing.