Only content you can access appears here. Use Tab or arrow keys to browse; Enter to open.

Start deploying
On this page

Domains and DNS

Connect, purchase and renew a domain

A domain is a name such as example.com. DNS records tell the internet where its website and email services are located. Nameservers host those records. A domain purchase, a DNS change and an application deployment are separate operations; completing one does not complete the others.

Before you start

  • You need control of the domain or permission to purchase it, access to the correct workspace and a record of its existing DNS settings. Preserve mail records before any nameserver change. If the domain already serves a website, plan the change so you can verify the new destination before retiring the old one.

Use a domain you already own

  1. 1Open Hosting > Domains and add the root domain without a URL path.
  2. 2Complete the ownership check shown by GD. Access to a workspace does not prove ownership of an external domain.
  3. 3Review scanned or imported DNS records. Confirm website, email and verification records against the old provider; an automatic scan may not find every record.
  4. 4If using GD-managed DNS, change the registrar's nameservers to the exact values GD provides. Keep the old zone available until delegation and service checks succeed.
  5. 5If keeping DNS elsewhere, add only the records GD instructs you to create at that provider. Adding records in an inactive zone will not affect public DNS.
  6. 6Connect the intended hostname to the application and verify both DNS and HTTPS.

Buy a new domain

  1. 1Use the available domain search/purchase flow and check the exact spelling and extension.
  2. 2Review availability, term, registration price and renewal information. An available search result is not a completed registration.
  3. 3Enter accurate registrant/contact details and choose the intended customer or ownership association where offered. Registrant information identifies the domain contact; it is not simply the hosting server's address.
  4. 4Review the cart and payer, then complete payment once.
  5. 5Wait for the registration order to complete and follow the verification message sent to the registrant contact. Payment alone does not verify the email address.
  6. 6Return to GD to check domain status, then connect DNS and the application.

Handle contact verification

Check the contact mailbox, including spam, and complete verification before the stated deadline. If the address is wrong, correct it through the supported domain contact workflow or support, then request the appropriate verification process. Updating contacts may trigger another verification or registrar restriction. Do not assume every registrar message can be disabled or that GD replaces all mandatory notices.

Connect root and www

The root domain and www are different hostnames. Decide whether both should open the app and which should be the preferred address. Add each hostname through the application/domain workflow, use the records shown, then test both HTTPS addresses and redirects. Do not point a hostname at an arbitrary server IP copied from another app.

HTTPS or CDN is pending

HTTPS needs a valid certificate for the exact hostname. Confirm DNS reaches the expected destination before retrying certificate issuance. CDN setup is a separate delivery layer; use the settings available for the domain and check its status. Do not repeatedly change proxy/DNS modes without understanding the required configuration. Never remove email records while troubleshooting a website certificate.

Renew a domain

  1. 1Review the expiry date early in Domains.
  2. 2Choose the available renewal term and review its price and payer.
  3. 3If AutoPay is offered, check its saved setting and eligible mandate. Otherwise complete manual renewal.
  4. 4Confirm the registrar/domain expiry date advances after the renewal completes. A payment pending state is not proof of renewal.
  5. 5If expired, inspect the available recovery path and price. Normal renewal, grace and redemption are different states; contact support when the interface cannot renew it.

If something does not work

  • Wrong website: verify the hostname's current DNS and connected app. Email stopped after nameserver change: compare MX, SPF, DKIM and other mail records with the original zone. Domain suspended: check registrant verification and renewal status. DNS changes seem ignored: verify which nameservers are actually authoritative and allow caches to expire. Keep a copy of old records for recovery.

Expected result

The correct application opens through HTTPS at each intended hostname, email still works, ownership/contact verification is complete and the domain's expiry date matches the completed registration or renewal.

Open the relevant page, then confirm the workspace or administrative context before making changes.

Open Domains

Related guides and references

For signed-in procedures, open Help in your workspace and search by the task name. Administrative guides require the internal-documentation permission.