@maturcotte Also, just to clarify. The whois information won’t change when you mess with DNS. Some domain providers show the name servers on the whois but that is on their end and not how you system actually pulls information on “where to go” when you make a request for it. You can use tools like nslookup domain.tld and dig NS domain.tld. Also, a ping won’t happen unless you add an A and/or AAAA record to the DNS configuration.

@maturcotte

You may also want to use a tool, such as this one, to see what the “root servers” are reporting for your domain. This will give you an idea of how far the resolution has gone thus far. If all RS are reporting the new DNS, then it most likely is your ISP’s local cache or browser cache that is the issue.

I remember a while back, my ISP, Charter Communications, used to heavily cache requests, so much that DNS would take nearly 3 days every after flushing everything on my entire network (that I had access to). After numerous complaints, it seems that they’ve let up on this a bit as it was causing some major headaches.

Of course, you can always force-resolve your domain using the Windows hosts file, or for *nix, the /etc/hosts file. Simple drop in an entry that looks like:

DROPLET_IP yourdomain.ext www.yourdomain.ext

… (this applies to both Windows & Linux), save and then, if it doesn’t automatically resolve, do a quick reboot.

Note: This modification would go on your local PC/Laptop, not the Droplet, just to be clear :-).