You own a domain. You have an Omega Digital hosting account. Making them talk is one of two small changes at your registrar. Which one you pick has real consequences for how you manage DNS going forward, so this article explains both.
Option 1: Change nameservers (recommended for most)
This hands all DNS for the domain to Omega Digital. You manage records from cPanel, and we handle MX, SPF, DKIM, and A records automatically when you add services. Fewer moving parts, fewer ways to misconfigure.
- 01. Log into your registrar (Namecheap, GoDaddy, Porkbun, etc.).
- 02. Open the domain's DNS/nameservers settings.
- 03. Select Custom nameservers.
- 04. Enter the two nameservers from your welcome email, typically: ns1.omdigital.cc and ns2.omdigital.cc.
- 05. Save. Propagation usually completes in under an hour; worst case, 24 hours.
# Verify the nameserver change
dig +short NS yourdomain.com
# Expected output
# ns1.omdigital.cc.
# ns2.omdigital.cc.Option 2: Keep existing nameservers, add an A record
This keeps DNS at your current host (Cloudflare, AWS Route 53, Namecheap's built-in DNS, and so on) and simply directs web traffic to our IP. Choose this if you already manage DNS centrally across multiple services, or if you want Cloudflare's proxying and caching in front.
- 01. Find the server IP in your welcome email (e.g. 198.51.100.42).
- 02. At your DNS provider, create or edit an A record: host @, value 198.51.100.42, TTL 3600.
- 03. Create a second A record: host www, same IP.
- 04. If you use Omega Digital for mail, also add our MX records; otherwise point MX wherever your mail lives.
- 05. Save.
If you choose option 2, you are responsible for MX, SPF, DKIM, and any other DNS records. AutoSSL in cPanel still works because it uses HTTP validation, not DNS.
Which one should you pick?
| Situation | Recommendation |
|---|---|
| One domain, one site, no other services | Option 1: change nameservers |
| Already using Cloudflare proxying | Option 2: A record at Cloudflare |
| Using Google Workspace for email | Either works, both require correct MX |
| Running multiple subdomains on different hosts | Option 2: keep central DNS |
| Not sure | Option 1: it's simpler to undo than to untangle |
A full example: Namecheap → Omega Digital
Walk-through for the nameserver swap on Namecheap, the most common flow we see:
- 01. Log into Namecheap and open the Domain List.
- 02. Click Manage next to the domain.
- 03. In the Nameservers section, switch from Namecheap BasicDNS to Custom DNS.
- 04. Enter ns1.omdigital.cc and ns2.omdigital.cc.
- 05. Click the green checkmark to save.
- 06. Wait 30–60 minutes, then run dig +short NS yourdomain.com to confirm.
After the change
Once nameservers or A records are live, issue SSL under cPanel → SSL/TLS Status → Run AutoSSL. Certificates validate by HTTP and should issue within one to five minutes.
Common gotchas
- · Entering the nameservers in the wrong field. Nameservers are different from Glue records or DNS records.
- · Mixed configurations. Pointing A records at us while nameservers are still at your registrar sometimes works but creates lag and confusion. Pick one model.
- · DNSSEC left enabled. If your old host signed the zone and you change nameservers without removing DS records, resolvers refuse to answer. Turn off DNSSEC before the switch, then re-enable from the new side.
- · Thinking propagation is instant. It almost never is. Give it up to 24 hours before assuming something is broken.
Still stuck?
Email [email protected] with your domain name and the nameserver output from dig.