TL;DR (copy/paste for your registrar)
Set both of these nameservers at your domain registrar:
ns1.hosted-server.net
ns2.hosted-server.net
You don’t need to add IPs. Remove any old nameservers.
How our DNS works (why it’s fast & resilient)
Our DNS edge is built for high availability and low latency:
Anycast front doors:
ns1.hosted-server.netandns2.hosted-server.netannounce globally via anycast. Your resolver automatically reaches the nearest edge location.Regional load balancers: The anycast edge forwards queries to a local load balancer in-region.
Authoritative clusters: That load balancer sends the query to the closest authoritative DNS servers hosting your zone.
If a location has an issue, traffic automatically shifts to the next closest site—no changes required on your end.
Before you switch (recommended checklist)
Create/verify your zone in HostBible and make sure all records (A/AAAA, CNAME, MX, TXT—SPF/DKIM/DMARC, SRV, etc.) are present.
If you control the current DNS, lower TTLs (e.g., to 300 seconds) at least a few hours before you switch to speed up propagation.
If DNSSEC is enabled at your current provider, note it and plan the handover (see DNSSEC section below).
Plan a maintenance window if the domain is business‑critical (web & email).
Step‑by‑step: point your domain to HostBible
Sign in to your domain registrar (where you bought/renew the domain).
Open the Nameservers or DNS section for your domain.
Choose “Custom nameservers” (wording may vary).
Enter both nameservers exactly as shown:
ns1.hosted-server.netns2.hosted-server.net
Remove any old nameservers.
Save or Update. The registry will publish the new delegation.
Wait for caches to refresh. Most updates are visible quickly, but some resolvers may cache for up to the previous TTLs.
No glue records needed: Because our nameservers are under a different domain (hosted-server.net), you don’t need to register host records at your registrar.
Verify the change
Use any one (or all) of these checks after updating your registrar:
Check the delegation (NS):
# Linux/macOS dig NS yourdomain.com +short # or nslookup -type=ns yourdomain.com
Query a record directly at our anycast nameserver:
dig @ns1.hosted-server.net yourdomain.com A +short
Test via public resolvers (helps spot caching):
dig @1.1.1.1 yourdomain.com A +short # Cloudflare dig @8.8.8.8 yourdomain.com A +short # Google dig @9.9.9.9 yourdomain.com A +short # Quad9
If the NS results show only ns1.hosted-server.net and ns2.hosted-server.net and your A/MX/TXT queries return expected answers, you’re live.
DNSSEC handover (if applicable)
If DNSSEC was enabled with your previous DNS provider:
Disable DNSSEC at the registrar (removing the old DS record) before switching the nameservers, or switch NS and then promptly update the new DS record from HostBible.
Once your zone is live on HostBible and serving DNSSEC, add the new DS record at the registrar.
A mismatched or stale DS record can cause SERVFAIL (site appears down). When in doubt, temporarily remove the DS record, confirm resolution, then re‑enable with the new DS.
Email safety checks (don’t skip)
Make sure the following exist in your HostBible zone before you switch:
MX records for your mail provider
SPF (TXT), DKIM (TXT), DMARC (TXT) policies
Any autodiscover/autoconfig and mail. host records you use
Propagation & caching tips
Most resolvers respect TTLs; many changes are visible within minutes, but allow up to 24–48 hours worldwide in the worst case.
After switching, you can raise TTLs back to typical values (e.g., 1–4 hours for stable records).
Local cache flush commands (optional):
Windows:
ipconfig /flushdnsmacOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSRespondersystemd‑resolved:
sudo resolvectl flush-caches
Delegating only a subdomain to HostBible (advanced)
If you want only sub.yourdomain.com on HostBible while keeping the parent elsewhere:
In the parent zone (
yourdomain.comat the current provider), add NS records atsubpointing to:ns1.hosted-server.netns2.hosted-server.net
No glue is required (our NS are out‑of‑bailiwick).
Create the
sub.yourdomain.comzone in HostBible and add your records there.
Common issues & quick fixes
SERVFAIL after switching: Likely DNSSEC mismatch. Remove the old DS at the registrar or replace it with the HostBible DS.
NXDOMAIN / domain not resolving: Ensure the zone exists in HostBible and contains necessary records before switching NS.
Only one nameserver set: Many registrars require at least two—add both
ns1andns2.Old answers still appear: That’s caching. Check TTLs, test via multiple public resolvers, and consider flushing local caches.
Email disruption: Missing MX/SPF/DKIM/DMARC. Add/verify these in the HostBible zone, then re-test.
Best‑practice TTLs (guidance)
Web/app A/AAAA/CNAME: 300–1200 seconds
MX/TXT (SPF/DKIM/DMARC): 3600–14400 seconds
Stable records (rarely change): up to 24 hours
FAQ
Do I need to enter IP addresses for the nameservers?
No. Just the hostnames: ns1.hosted-server.net and ns2.hosted-server.net.
Can I use vanity nameservers like ns1.yourdomain.com?
If you need branded/vanity nameservers, contact HostBible Support to discuss options.
Is two nameservers enough?
Yes, our anycast edge and regional load balancing distribute queries across multiple backend clusters for resilience and performance.
Will switching nameservers break my site?
Not if your HostBible zone is complete. Prepare your records first, lower TTLs, then switch.
Copy/paste block (for registrar forms)
ns1.hosted-server.net ns2.hosted-server.net
If you’d like us to review your zone before you flip the switch, just share your domain and we’ll double‑check the records.