Thinking this through for a moment, and someone please correct me if my thinking is incorrect here.Assume no cache is used throughout and the domain name needs to be resolved to find the web host's IP address.The information that we would get as a result of this query will be something like: Now, won't these IP address that are being returned be out of date?
However, you need to ensure that you apply the same principals described above: 1. Remember, the IP addresses for your ns1 and ns2 A Records (and for your Glue Records) come from you--in that you have to set up at least two VPS to run your name servers. Login to your domain name registrar's control panel and create Glue Records for as many nameservers you wish to deploy.
See How to Setup DNS Slave Auto Configuration Using Virtualmin/Webmin on Ubuntu; How to Install the BIND DNS Server on Cent OS 6; or How To Install Power DNS on Cent OS 6.3 x64 1. In another words, associate (or map) Digital Ocean's nameserver IPs with your vanity nameservers' hostnames.
First, login to your Digital Ocean Control Panel and add your domain name to the Digital Ocean DNS Manager. Then, create A Records for your vanity nameservers and point them to Digital Ocean's IPs for ns1.digitalocean.com; ns2.digitalocean.com; ns3. With Go Daddy, for example, simply login to your Domain Name Control Panel and look for the area where you can list Host Names. The simplest way to configure DNS is to have someone else do it.
Circular references exist where the nameservers for a domain can't be resolved without resolving the domain they're responsible for.
If you are not able to determine how to create Glue Records at your particular domain registrar (that is, how to "register a nameserver or host name"), then you need to contact your registrar directly and let them know that you need to register a nameserver.