🔍

Managing subdomains in your HostGator account

Subdomains give each service, campaign or location its own web address without requiring another domain purchase. A site at example.com.au can use shop.example.com.au, events.example.com.au or staging.example.com.au while all addresses remain in one HostGator account. They are useful for a separate department site, a campaign landing page or a test copy kept away from the public website. Careful planning keeps these addresses consistent, secure and easy to maintain.

Managing subdomains in HostGator means coordinating three layers: cPanel, where the address and document root are created; DNS, which directs browsers to the server; and File Manager or FTP, where content is uploaded. A saved address that returns “404 Not Found,” an old page or a certificate warning often indicates a mismatch between those layers. This routine suits small Australian businesses, established organisations and anyone maintaining a local web presence.

Subdomains within a hosting account

A subdomain is a child of an existing domain. It does not replace example.com.au, become a separately registered domain or require its own renewal. HostGator can host several subdomains from one plan by giving each a document root while sharing account resources. An add-on domain is different: it is another base domain that must be registered or transferred and may need its own hosting arrangement.

Choose names for purpose and brevity, not internal department labels. Short addresses are easier to type on a phone, print on signage around Melbourne or Brisbane, or remember after a television advertisement. Avoid hyphens, years and sensitive project codes unless there is a strong reason to include them. A descriptive name also helps support staff or an agency locate the correct folder later.

Australian organisations often use .com.au. Registration rules for that suffix require eligibility and may call for an ABN, ACN or trademark evidence, depending on the registrant. Those rules apply to the parent domain; creating shop.example.com.au does not create another .com.au registration. A name such as sydney.example.com.au can identify an audience, but it does not prove a physical location or automatically improve search visibility.

Creating a subdomain in cPanel

Sign in to the HostGator customer portal and open the cPanel shortcut for the hosting account. In cPanel, search for “Subdomains” or open Domains and locate the subdomain controls. The exact screen depends on the cPanel theme, but the key fields are the complete hostname, parent domain and document root. Enter only the new label, such as events, where the interface already supplies example.com.au.

Select a document root that does not contain the main website. HostGator commonly uses public_html, so public_html/events may be suitable. Check the suggested path before saving because a wrong choice can expose unrelated files or overwrite an existing site. The folder may be created automatically, but confirming its name, owner and permissions first makes later troubleshooting easier.

Add an index page through File Manager, FTP or the file editor. A simple test page should display the hostname, a contact route and a link to the main site. Upload the real content only after that page appears at the new address. Keep production and test files in separate roots, remove obsolete defaults and record each hostname and path in the account documentation.

Managing DNS and propagation

Many HostGator installations create a DNS entry automatically, while some accounts require an A, AAAA or CNAME record in the domain zone. An A or AAAA record points to the server; a CNAME points to another hostname. Confirm the value instead of treating a saved cPanel form as proof that DNS is correct. Nameservers are normally managed at the parent domain’s registrar and need not change when an existing zone serves the new address.

DNS changes need time to pass through resolver caches. Lower the relevant record’s time to live at least a day before a planned migration, although no support team can force every resolver to refresh. Australian teams should note daylight saving: Brisbane stays on AEST, while Sydney and Melbourne alternate between AEST and AEDT. Record cut-over times in UTC as well as local time to prevent confusion across Perth, Adelaide and overseas.

Test from a clean browser after the address resolves. It must show the intended page, the correct HTTPS certificate and no unexpected redirect. Account SSL/TLS or AutoSSL tools should cover the exact hostname, including www when used. Tools such as dig and nslookup can confirm whether the A, AAAA or CNAME record has propagated. If records conflict, remove the obsolete destination rather than leaving both active.

Protecting files and mail services

A hostname makes files in its document root reachable unless server rules block them. An empty folder or hidden filename is not adequate protection for drafts, backups, database exports or configuration data. Keep private files outside public_html, use File Manager privacy settings where available, and give maintenance users only necessary permissions. Password protection on a staging page can supplement, but not replace, proper access controls.

Subdomains do not automatically receive separate mailboxes. An address such as events@example.com.au is created through Email Accounts and normally shares the hosting account’s storage. Before redirecting a form or support address, check email quota usage to avoid accepting mail that cannot be stored. Mail routing also needs suitable MX records, so use HostGator’s email tools rather than copying every DNS record from the main domain.

Test the full form path: submission, confirmation, error handling, spam control and mailbox delivery. If it collects personal information, check the notice, consent process and retention settings against applicable Australian Privacy Act requirements; commercial email may also engage the Spam Act 2003. Keep analytics and advertising scripts off staging pages when they would pollute reports or expose non-public information. Back up files and databases before changing permissions.

Updating or retiring a subdomain

Treat a rebrand or replacement address as a migration. Build the destination, copy content, preserve useful metadata and test forms before changing links. Add a permanent server-side 301 redirect from the old hostname to the closest relevant replacement; sending every old address to the homepage loses context. Update navigation, invoices, QR codes and campaign material gradually, keeping the old hostname active while caches and search engines catch up.

A page of independent reviews can offer context when assessing a provider, but its author, date and ownership should be checked before a business relies on it. External links can disappear, redirect to unsafe destinations or lead to content that no longer matches the service described. Include outbound-link checks in release work rather than waiting for a customer report.

Before deletion, search databases, content and account notes for references to the hostname. Check email routing, analytics, scheduled jobs and integrations that might still depend on it. Use cPanel’s removal control rather than assuming that hiding a folder deletes DNS, and verify whether its matching zone entry is removed too. HostGator tutorials and the knowledge base can clarify routine tasks, while a ticket containing the hostname, timestamps, DNS values and screenshots is more useful than a general request to check the site. Never include passwords, private keys or billing details in a ticket or public forum.

A practical subdomain routine

Use the same owner, naming rule and review date for every hostname. Check a new address after creation, after a migration and at least quarterly. Test the live page as well as the cPanel record, since a correct folder can still have stale DNS or an expired certificate. Keep registrar contacts separate from technical contacts so staff changes do not leave inaccurate records. An automated crawl can also flag redirects and failed outbound URLs. It may encounter a campaign reference such as a live Bitcoin payout page; open the destination in a private window, confirm its final domain and check that any Australian age-restricted gambling, responsible-gambling or financial wording suits the linking site. Referencing a page does not transfer permission to reuse its content.

Each release can be checked against this compact list:

Planned removals need a different safeguard:

Account housekeeping belongs in the same routine. Review invoices through HostGator’s billing portal, confirm renewals for the parent domain and hosting service, and check that Australian customer details and GST treatment appear correctly. Record every change in the knowledge base or an internal account note, and use forums or ticket support for reproducible DNS and cPanel problems. The durable lesson is that a subdomain is one coordinated system: create the destination, verify DNS and HTTPS, publish tested files, preserve a rollback and allow for propagation before retiring an old address.