Trusted Web Hosting | SECURE_INFRA: CAN_NODE_01 | ENCRYPTION: AES-256-GCM | Documentation |
Domains & DNS

How to Point Your Domain's Nameservers to CyberNet

Published on Jul 29, 2026 Updated on Jul 30, 2026 3 views

If your domain is registered somewhere other than CyberNet (or you registered it separately from your hosting), you'll need to point its nameservers to us before your website and email will work.

CyberNet Nameservers

Use the following two nameservers:

  • ns1.cybernet.host
  • ns2.cybernet.host

How to Update Nameservers

The exact screen varies by registrar, but the steps are generally the same:

  1. Log into your domain registrar's account (GoDaddy, Namecheap, or wherever the domain is registered).
  2. Find your domain and open its DNS or Nameservers settings.
  3. Switch from "default"/"parked" nameservers to custom nameservers.
  4. Enter ns1.cybernet.host and ns2.cybernet.host.
  5. Save your changes.

If your domain was registered directly through CyberNet, you can also update nameservers from your client area under My Domains without needing to log into a separate registrar.

How Long Does It Take?

Nameserver changes typically propagate within 1-24 hours, though it can take up to 48 hours in rare cases as the change spreads across DNS servers worldwide. Your site and email will start working as soon as propagation reaches your location.

Checking Propagation

You can check whether your new nameservers are live using a tool like dnschecker.org — search for your domain's NS records and confirm they show ns1.cybernet.host and ns2.cybernet.host globally.

Common Mistakes

  • Typos in the nameserver address — copy-paste rather than typing them manually.
  • Editing individual DNS records instead of nameservers — if you want to keep DNS management with your current registrar instead of moving it to CyberNet, ask our support team for the correct A/CNAME records instead.
  • Domain locked at the registrar — some registrars require you to unlock the domain before nameserver changes are allowed.

Back to Knowledgebase: Knowledgebase
Was this helpful?