https://help.1and1.com/domains-c36931/manage-domains-c79822/dns-c37586/explanation-of-a-glue-record-a595844.html

(Quote)

Looks fine to me now. I'm not sure what happened but this was how it looked to me right after I finished ordering a domain. @Falzo maybe you're right, could be my DNS poisoned.

https://dns.he.net/

* Change your DNS or whatever and wait until everything propagates

But if i change IP, then the DNS propagation will be involved which means people with cached old IP will still go to old server and de-synchronize things unless i shut down old server or setup some ip

Don't forget to alter your DNS TTL now, so you can have your zone cached for less time to prep for migration. After all's good and done, change your IPs in DNS and then put the TTL back.

* Point your dns to your new server.

Spin two VM, one existing, one new. Do rsync to new VM from old, when complete then slowly start pushing traffic to new VM via DNS, upon no traffic for a period greater than 20 minutes, shutdown old V

I used to use he.net/afraid.org/zoneedit back in the day, but running your own secondary DNS is the easiest thing in the world. Just copy over your config, s/master/slave, tell it the master NS, setu

(Quote)

dns.he.net, CloudFlare

Now to find some secondary/slave DNS for redundancy!

(Quote)

Try our DNS hostio dnsmanager.io

Yes, just click on the cloud so it turns gray which will turn off all the cloudflare stuff and only use their DNS. I have over a hundred domains using Cloudflare's free DNS and it's the best free dns

1984's FreeDNS doesn't support SPF domains.

* Free reverse DNS management

how difficult to maintain 100% uptime, unless you completely useless at managing server? I havents seen any DNS services less than 100%

(Quote)