Skip to main content

IP Address Changes on Shared Hosting

Justin Catello avatar
Written by Justin Catello
Updated today

Important: Upcoming IP Address Changes on Shared Hosting Servers (Action May Be Required)

We’re making a large network change across several of our shared hosting servers, and some customers will need to update their DNS records before December 31, 2025 to avoid downtime.

We want to be completely transparent about what’s happening, why it’s happening, and who actually needs to do anything.

Why are IPs changing?

When we first started out (over 15 years ago), part of our infrastructure lived in a suite operated by Hivelocity. At that time, we rented IP space assigned to that suite.

Recently, that suite was handed back from Hivelocity to the building / datacenter operator. As part of that change:

  • The rented IP ranges associated with that suite are being reclaimed.

  • We cannot continue to use those specific IP ranges going forward.

  • The good news: we now own all of our own IP ranges for new and existing infrastructure, so this is a one-time cleanup of very old, rented space.

Because of this change of ownership, we’re being forced to move a number of servers off those old IPs and onto IPs that we fully control.

That means:
👉 Server hostnames stay the same
👉 Your data and services stay on the same server
👉 But the server’s public IP address is changing

Who needs to take action?

It depends on where your DNS is managed and whether you’re using our nameservers.

✅ No action required if:

  • Your domains use BigScoots nameservers, or

  • We manage your DNS zone inside our platform.

In these cases, we will update the IPs for you on our end. You don’t need to change anything, and your site will continue to work normally.

🧑‍💻 Action required if:

You do not use our nameservers and instead:

  • Use Cloudflare (or another CDN) and you’ve set the origin IP manually, or

  • Use custom DNS at your registrar (GoDaddy, Namecheap, etc.) with an A record pointing directly to your server’s IP, or

  • Manage DNS on your own server or third-party DNS provider and reference our IP directly.

In these cases, you will need to:

  1. Find your server in the list below.

  2. Note the new IP address for that server.

  3. Update all A records (and any other records pointing to the old IP) to use the new IP instead.

⏰ Deadline:
All old IP ranges will be shut down on December 31, 2025.
Any domains still pointing to the old IPs after that date will go offline until their DNS is updated.

Notes about dedicated IP addresses

As part of this cleanup and to prepare for the long term, we are also:

❌ No longer offering dedicated IPs on shared servers

Due to IPv4 exhaustion and best practices going forward:

  • We will no longer assign per-site dedicated IPs on shared hosting servers.

  • All sites on a shared server will now use the server’s main shared IP.

This means:

  • If your site previously had its own dedicated IP on a server,

  • You should now update your DNS to use that server’s new shared IP, not your old dedicated IP.

Functionally:

  • SSL/TLS: Modern SSL works via SNI and does not require a dedicated IP.

  • SEO & reputation: Shared IPs are the industry norm and are not a negative signal by themselves.

  • Firewalls / whitelists: If you’ve whitelisted the old dedicated IP anywhere (APIs, payment gateways, etc.), you’ll need to update those whitelists to the new shared IP.

We’re happy to help you verify what needs updating if you’re unsure.

Server list – old IP → new IP

Below is where you’ll find the full list of affected servers. For each, we’ll show:

  • Server name

  • Hostname

  • Old IP (being retired)

  • New IP (to use going forward)

Example: Server “Peter”

Server name: Peter
​Hostname: peter.securedserverspace.com

  • Old IP: 50.31.99.15

  • New IP: 216.185.212.184

If you do not use our nameservers and you have any DNS records pointing to 50.31.99.15 or to any other IP on that server, you should:

  • Change those records to point to: 216.185.212.184

🔁 General rule for every server in this list:


If your site is on that server and is pointed to any IP other than the new one listed, you must update your DNS to point to the new IP for that server.

How to update if you use Cloudflare

If your site is behind Cloudflare:

  1. Log in to Cloudflare.

  2. Go to the DNS tab for your domain.

  3. Find all A records that currently point to your old server IP.

  4. Update those to the new IP for your server (from the table above).

  5. Leave the orange/grey cloud setting (proxy/DNS-only) exactly how it was before.

You do not need to change nameservers at Cloudflare – you’re only updating the origin IP.

How to update if you use DNS at your registrar / external DNS

If your DNS is hosted at your domain registrar or a third-party DNS provider:

  1. Log in to your registrar / DNS provider.

  2. Open the DNS / zone editor for your domain.

  3. Find A records like:

    • @ (root domain)

    • www

    • mail (if you’re pointing that to our server for mail)

    • any other custom hostnames that point to the old IP

  4. Change them to the new IP for your server.

  5. Save and allow DNS to propagate.

What happens if I don’t update by December 31, 2025?

  • The old IP ranges will be removed from service.

  • Any domain that still points to an old IP will:

    • Stop resolving correctly and appear offline,

    • Until its A records are changed to the new IP.

As soon as your DNS is updated to the correct new IP, your site will come back online (assuming no other configuration issues).

FAQ

Q: Do I need to change my nameservers?
​A: No, not unless you want to move your DNS to us. If you’re using our nameservers already, we’ll handle everything for you. If you’re using Cloudflare or another DNS provider, you just need to update the IPs in your existing DNS.

Q: Will SSL certificates break?
​A: If we manage SSL on your account (AutoSSL / Let’s Encrypt via cPanel), we’ll ensure certificates continue to function. SSL is tied to domains, not to a specific IP, and modern SSL supports SNI, so a dedicated IP is not required.

Q: My site had a dedicated IP before – is that going away?
​A: Yes. All sites on shared hosting will now use the server’s shared IP. You’ll need to update any DNS records or whitelists that reference your old dedicated IP to the server’s new shared IP.

Q: My site is still down after I updated DNS – what do I do?
​A: Open a ticket with us and include:

  • Your domain name

  • The server name (from the list)

  • A screenshot or copy of your current DNS records

We’ll help verify everything and get you back online.

Need help?

We know IP changes are annoying and not something you asked for. Unfortunately, this datacenter ownership change means these specific ranges are being taken away, and we have no way to retain them.

What we can do is:

  • Make the transition as smooth as possible,

  • Handle everything automatically for customers on our nameservers,

  • Provide clear instructions and one-on-one help for anyone using custom DNS.

If you’re unsure where your DNS is hosted or how to make these changes, reach out to support and we’ll walk through it with you.

Did this answer your question?