Member Avatar for jkon

First of all let me clarify that I am programmer and that my knowledge in system administration are limited ( I know more than that limited spectrum but I wouldn’t trust me on those ). This idea arose out of two deferent needs , I have a dedicated server in one hosting company with only two IP’s and I am thinking to rent two more per month because I don’t want some of the accounts there to have the same IP’s resolving name servers as the others. The second need is that I am thinking to change hosting company at all and I have seen in the past that when you change name servers can take a while.

I will express my thoughts and please correct me if I got it wrong. It could be a service – company that would rent IP’s and redirect them to what ever IP you would like, more over you could adjust the name servers of a domain to point to that IP. In that way when you change a hosting company for example you wouldn’t have to change IP’s in your name servers. Are there companies providing that ? And with what cost in resources out of the redirection process?

  • 2 Contributors
  • 3 Replies
  • 439 Views
  • 5 Hours Discussion Span
  • Latest Post Latest Post by JorgeM

Dani AI

Generated

Short expert summary and practical path forward (for , building on ’s suggestion): if domestic ISPs ignore TTLs you can either front your nameserver with a single, stable public IP that you control (and remap the backend), or let a DNS/CDN provider front and proxy traffic so the public IP never has to change. Both approaches avoid asking users to change DNS settings and avoid long registrar/TLD glue churn. (ionos.com)

Option A — reserved/floating/elastic IP + tiny reverse proxy: allocate a static IP from a cloud/VPS provider (Elastic IP on AWS, Floating/Reserved IP on providers like DigitalOcean) and use it as the glue for ns1/ns2. Run a small Nginx/HAProxy instance on that IP and proxy to your real hosts; when you move hosts you either reassign the reserved IP or change the proxy target. This gives a single constant IP at the parent zone. Check provider limits (region, PTR/reverse-DNS and mail caveats). (docs.aws.amazon.com)

Option B — managed DNS/CDN or vanity nameservers: use a provider that proxies/load-balances for you (Cloudflare, other CDNs or managed DNS with vanity nameservers). Proxied records return the provider’s global/Anycast IPs while you update the origin in their dashboard — no glue change required. Some providers offer “custom/vanity nameservers” so you keep branded ns1.domain.tld while they host the back end (often a paid feature). (developers.cloudflare.com)

Quick checklist before you migrate:

  • Lower the TTL (e.g., to 300s) at least 24–48 hours before a cutover.
  • Create the reserved/floating IP or enable the provider proxy and set your glue to that IP.
  • Test with dig (+trace) and global DNS checkers.
  • Verify reverse DNS/PTR if you send mail (many floating IPs have restrictions).
    Example quick checks:
    dig +short NS example.com
dig +trace example.com
dig @8.8.8.8 ns1.example.com A

    Expect small monthly/hourly fees or bandwidth charges from providers; review their docs/pricing before committing. (ionos.com)

Recommended Answers

All 3 Replies

Member Avatar for JorgeM

I have seen in the past that when you change name servers can take a while.

When the DNS record is changed, it will take no longer than the Time To Live (TTL) setting on the record. Prior to making changes, if you lower this value to as low as possible, the DNS record cache will be lower, thereby seeing the "change" happen more rapidly.

company that would rent IP’s and redirect them to what ever IP you would like

What you are asking about is "renting" a virtual IP that reverse proxies a real server behind it. I personnal dont know of any providers that do this as a stand-alone service. I would tend to think, if the provider has this service, they would also provide hosting services for your website as well.

Again, i am not sure you need to get into the virtual IP scenario... I would suggest that you host your DNS records with a provider that allows you to manage the TTL of the records in a manner that you can temporarily set the record to a very low value so that when you make changes, the new values are resolvable by all clients.

Member Avatar for jkon

JorgeM thank you of making cleaner what I am asking and probably what I will not find ;)))

The problem is a bit more complex than I originally suggested.

I live in a country lets call it FC that the ISP’s of it don’t update their DNS servers for a while (for domestic name servers) . That means that if I have ns1.domain.fc pointing to one IP and then change it could take a month or two (I am not kidding) for the clients of that ISP, of course I couldn’t ask visitors of a site to use a public DNS …

Don’t start to talk about how they are permitting such thing. They don’t, and they are in court about that as well, but it is not my main consideration. If I could find an IP provider (front office) that I could change the IP behind it (back office) without any severe resource cost would be great.

Again thanks JorgeM for making me searching virtual IP … hope some day that idea to flourish.

Member Avatar for JorgeM

Basically from what I understand, you simply need a provider that provides Load Balancing/Reverse Proxy services. Continue searching on that note...

keep us updated on your findings. It may help someone else in your situation.

commented: Thanks for taking the time to place it in a proper way what I am looking for +6
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.