DNS not resolving after updating the Nameservers of to DO. SPF are not resolving

Posted June 20, 2019 1.1k views


*** can’t find Non-existent domain

nslookup -q=mx
primary name server =
responsible mail addr =
serial = 1561011523
refresh = 10800 (3 hours)
retry = 3600 (1 hour)
expire = 604800 (7 days)
default TTL = 1800 (30 mins)

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers


Everything looks ok for the parent domain “” when I try my own ns lookups but does not look like any other records beyond the basics have been setup.

After switching to a new DNS provider like DIgitalOcean you’ll need to create any additional records like “www” or “web” hostnames, or MX records.

Here’s a link to the Quick Start doc on using DO’s DNS administration panel in Cloud:

It contains links to other docs and tutorials for tasks like setting up new hostnames or MX records.

Hope this helps, let us know if you have any more questions :)

  • I had already installed WHM cPanel and updated the records more than 12 hours back. Only domain is resolving but the other records resolving to SOA records. I had checked the DNS file and records are present but it’s not resolving. Updated SPF too but not working.

    • I’m not overly familiar with WHM cPanel but I believe the DNS management inside of cPanel only works when the server it is running on is also the DNS server that the domain is delegated to.

      Currently, your domain is delegated to DigitalOcean’s name servers so only changes you make via your DigitalOcean Cloud account or API will take effect.