HostBible Nameservers: NS1 & NS2 and How to Point Your Domain

If you've registered your domain elsewhere and want it pointing to your HostBible hosting account, you need to update your nameservers. This guide covers HostBible's official nameservers, what nameservers actually do, step-by-step instructions for the most common registrars, how to verify the change worked, and what to do if things go wrong.

HostBible's Official Nameservers

HostBible's two authoritative nameservers are:

These are the same nameservers regardless of which HostBible hosting plan you are on. Web hosting, WordPress hosting, reseller hosting, and VPS plans all use these two nameservers unless you have configured a custom nameserver setup. You only ever need these two entries, no IP addresses are required at the registrar.

What Nameservers Do

A nameserver is a DNS server that holds the authoritative records for your domain. When someone types your domain into a browser, their device asks the global DNS system: "who is in charge of this domain?" The registrar's record points to your nameservers, and those nameservers then answer all the DNS questions for your domain, which IP address to reach, where to send email, which subdomains exist, and so on.

Changing nameservers transfers that authority from your old host to your new one. Once the change propagates, all DNS queries for your domain are answered exclusively by HostBible's nameservers. This is why it's important to ensure your DNS records are fully set up on the new side before making the switch.

Step-by-Step: How to Update Your Nameservers

The process is the same regardless of where your domain is registered. Log in to your registrar, find the domain, and look for a "Nameservers" or "DNS" section. You will switch from the current nameservers to custom ones and enter HostBible's values.

General steps (any registrar)

1. Log in to your registrar's control panel.
2. Navigate to your domain list and select the domain you want to point to HostBible.
3. Find the Nameservers section. It may be labelled "DNS Settings", "Manage DNS", or "Name Servers".
4. Switch from default or existing nameservers to custom nameservers.
5. Enter NS1.HOSTED-SERVER.NET as the first nameserver.
6. Enter NS2.HOSTED-SERVER.NET as the second nameserver.
7. Remove any additional nameservers that were previously listed (third, fourth entries).
8. Save the changes.

Registrar-Specific Instructions

The nameserver field is found in different locations depending on where your domain is registered. Here are the exact paths for the most common registrars.

GoDaddy

1. Log in and go to My Products.
2. Find your domain and click DNS.
3. Scroll to the Nameservers section and click Change.
4. Select Enter my own nameservers and enter the HostBible nameservers.
5. Click Save and confirm the change.

Namecheap

1. Log in and go to Domain List.
2. Click Manage next to your domain.
3. Under the Nameservers section, change the dropdown from "Namecheap BasicDNS" to Custom DNS.
4. Enter NS1.HOSTED-SERVER.NET and NS2.HOSTED-SERVER.NET.
5. Click the green tick to save.

Google Domains / Squarespace Domains

1. Log in and select your domain.
2. Go to DNS > Nameservers.
3. Click Switch to custom name servers.
4. Enter the HostBible nameservers and save.

IONOS (1&1)

1. Go to Domains & SSL and select your domain.
2. Click DNS then Nameserver.
3. Select Use custom name servers and enter the HostBible values.
4. Save the change.

Cloudflare Registrar

If Cloudflare is both your registrar and DNS provider, changing nameservers away from Cloudflare requires contacting their support, as Cloudflare-registered domains are locked to Cloudflare nameservers. An alternative is to keep Cloudflare as your DNS provider and configure HostBible's IP in an A record there, rather than changing nameservers. Contact HostBible support if you need guidance on this setup.

How Long Does It Take?

Nameserver changes propagate through the global DNS system as cached records expire. Each DNS resolver worldwide caches the old nameserver information for the duration of its TTL. In practice:

• Most locations: 1 to 4 hours
• Slower resolvers: up to 24 hours
• Worst case: 48 hours (rare, usually caused by an unusually high TTL set on the old nameservers)

You can check propagation progress from multiple global locations using our DNS Propagation Checker. Enter your domain and select the NS record type to see which parts of the world are already using the new nameservers.

To verify the change from the command line, query the authoritative nameservers directly:

dig yourdomain.com NS +short

Once you see ns1.hosted-server.net and ns2.hosted-server.net in the response, the change has propagated to that resolver.

Will My Site Go Down During the Change?

There is usually a brief transition period where different users see different results as the change spreads through the DNS system. Users whose resolver has cached the old nameservers will still reach your old host; users with a fresh cache will reach HostBible. To avoid any visible downtime, the recommended approach is to set up your site on HostBible fully before changing nameservers.

That way, regardless of which nameserver a visitor hits, they see a working site. If you are migrating from another host, keep that account active until propagation is complete and you've confirmed everything is working on HostBible's servers.

What Happens to Your Existing DNS Records

When you change nameservers, DNS authority moves entirely to HostBible. Any records you had configured at your old provider (custom MX records, SPF/DKIM TXT records, CNAME records for third-party services) are no longer active. HostBible's nameservers will serve only the records configured in your HostBible control panel.

Before making the switch, log in to your current DNS provider and note down every record you have configured. You'll need to recreate any custom records in your HostBible DNS zone. This is especially important for:

• MX records, email will stop working if these aren't transferred.
• SPF, DKIM, DMARC TXT records, email authentication will break without these.
• CNAME records for third-party services, Stripe, Zendesk, HubSpot, and similar integrations use CNAMEs that must be recreated.

Troubleshooting

The nameserver change doesn't seem to have taken effect

First verify the change actually saved at the registrar. Log in and confirm the nameservers shown are NS1.HOSTED-SERVER.NET and NS2.HOSTED-SERVER.NET. If they are correct but propagation hasn't completed, allow more time and use our DNS Propagation Checker to monitor progress.

My domain still shows the old host's content

Your local DNS resolver may still be caching the old records. Try flushing your local DNS cache or testing from a different network or device. You can also query Google's resolver directly to see what it's returning: nslookup yourdomain.com 8.8.8.8. If Google sees the new IP, the issue is purely your local cache.

I see a "domain parked" or blank page

The nameservers have updated but the domain hasn't been added to your hosting account, or the hosting account setup isn't complete. Log in to your HostBible client area and confirm the domain is assigned to your hosting package. Contact support if it is assigned but still not serving your site.

My email stopped working after changing nameservers

Changing nameservers transfers DNS authority entirely to HostBible. Any custom MX, SPF, or DKIM records you had at your previous provider are no longer active. Recreate those records in your HostBible control panel. Check your old DNS configuration before making the switch and document any records you need to transfer.

I entered the nameservers but my registrar is showing an error

Some registrars validate nameserver hostnames by resolving them. Enter the nameservers in uppercase as shown (NS1.HOSTED-SERVER.NET) or in lowercase (ns1.hosted-server.net), both are valid. If the registrar asks for IP addresses alongside the nameserver hostnames (this is called "glue records"), contact HostBible support for the current IP addresses for the nameservers.