Registering private nameservers using dynamic DNS

Question

Using a service such as no-ip links your domain to an IP address. For that to happen a client is installed on the web server using the no-ip username/password details.

So, www.example.com may point to 123.123.123.123. However, obviously being dynamic, www.example.com may suddenly change to 123.123.123.124.

The problem I have is with my domain registrar (Namecheap), when I register private name servers I have to link a domain to a fixed IP address. As it's dynamic, I can't assume www.example.com is always going to point to 123.123.123.123.

How do I get around this problem, without having a static IP provided by my ISP, as that means a business account and with that comes additional costs?

EDIT: I may have used private wrongly. I currently host my own webserver on a VPS, which has a static IP. However, I'd like to host my own webserver from home but my ISP doesn't provide a static IP unless I switch a business account (at an extra cost, of course). I host many other people's (only friends, so downtime here and there isn't a massive issue) websites, so I have my own nameservers - so it's easy for people to point their websites at my server. It's when using those nameservers I need to associate the nameserver with a fixed IP, hence the issue I'm having.

Answer 1

The way those dynamic DNS services work is that the agent that they install on your network updates the DNS record in near real time every time a new IP address is detected and maintain an extremely low time to live for the DNS records (often as low as just a few seconds) so that the DNS records basically never get cached by upstream DNS services. In order for you to achieve something similar for your system you would have to sign up with a white label DNS provider that supports real time agent record updates (I am not aware of any at the moment) or you would have to create your own agent that can remotely change the DNS records for you (getting rather complicated at this point).

I will point out though that most ISP's have restrictions in place on their networks (and automated detection to enforce the restriction) to prevent people using residential internet services to host websites. This is more often than not based on monitoring the download versus the upload bandwidth, a normal residential service will have mostly download and a very small (comparitively speaking) upload level whereas a connection that is doing some description of hosting will have a much higher than expected upload usage for the month. Given the costs involved in setting up an agent updatable DNS service and the risk of your residential service being cut for breach of terms of service compared to the costs of a small business connection which would support a static IP address and allow hosting you would honestly IMO be better off going for the small business service over the residential service. I don't know who your ISP is personally but the price difference between a residential service and a small business service (here in Australia at any rate) are minimal and you get significantly greater value out of the service on small business than on residential.