This guide explains how to use a domain you already own with GudisHub shared hosting. You keep the domain at your current registrar — you only change where DNS is served so the website (and mail, if you use it) points to GudisHub.

GudisHub nameservers:

• ns1.gudishub.net
• ns2.gudishub.net

You can also see these on your hosting service page in the client area under Nameservers.

Before you start

• You have an active GudisHub shared hosting service.
• You can log in to your domain registrar (where you renew the domain).
• You know whether email for this domain should stay at the current provider or move to GudisHub.

Step 1 — Add the domain in DirectAdmin (if needed)

1. Open my.gudishub.net and open your hosting service.
2. Click Log in to Control Panel (DirectAdmin).
3. If this domain is not already on the account:
   • Go to Domain Setup (or Account Manager → Domain Setup).
   • Add / create the domain (e.g. example.com).
4. Confirm the domain appears in the domain list.

If the domain was created automatically when you ordered hosting, you can skip adding it again.

Step 2 — Change nameservers at your registrar

1. Log in to the registrar where the domain is registered (OVH, GoDaddy, Namecheap, Cloudflare Registrar, .lt registry reseller, etc.).
2. Open the domain settings and find Nameservers / DNS servers / NS records.
3. Switch from “default / registrar DNS” to custom nameservers.
4. Set exactly:
   • ns1.gudishub.net
   • ns2.gudishub.net
5. Save the changes. Some registrars ask you to remove old NS values first.

Do not enter IP addresses in the nameserver fields — use the hostnames above.

Step 3 — Wait for DNS propagation

Nameserver changes usually take from a few minutes up to 24–48 hours worldwide (often under a few hours).

• Check public NS with: dig NS example.com +short — you should see ns1.gudishub.net and ns2.gudishub.net.
• Online checkers (e.g. DNSChecker) help confirm propagation in different regions.

Step 4 — Enable SSL

After DNS points to GudisHub:

1. In DirectAdmin, open SSL Certificates.
2. Issue a free Let's Encrypt certificate for the domain (and www if you use it).

SSL issuance fails if the domain does not resolve to your hosting account yet — wait for DNS, then retry.

Email (important)

When you switch to GudisHub nameservers, DNS for the domain is managed on GudisHub (DirectAdmin). That includes MX records for email.

• If you want email on GudisHub, create mailboxes in DirectAdmin and use the default MX GudisHub provides.
• If email must stay elsewhere (Google Workspace, Microsoft 365, another host), copy the existing MX (and related SPF/DKIM/TXT) records into DirectAdmin DNS before or immediately after changing nameservers, or mail will break during the switch.

Alternative: keep your current DNS (A records only)

If you prefer to leave nameservers at the registrar or Cloudflare:

1. In the client area / DirectAdmin, find your hosting account IP address.
2. At your current DNS provider, set:
   • A record for @ (and usually www) → that IP
   • Optional: AAAA if you were given IPv6
3. Leave MX/TXT for email as they are, unless you also move mail.

For most customers, GudisHub nameservers are simpler because DNS, website, and mail stay in one panel.

Troubleshooting

• Site still shows the old host: DNS not fully propagated, or browser/DNS cache. Wait and re-check NS with dig.
• SSL error / certificate pending: Domain not resolving to GudisHub yet — wait, then re-issue Let's Encrypt.
• “Domain already exists” in DirectAdmin: Contact support — the domain may still be assigned to another account.
• Mail stopped working after NS change: Restore MX/SPF/DKIM in DirectAdmin DNS to match your mail provider.

Need help? Open a ticket from the client area or email [email protected].