moving DNS from Bluehost to DigitalOcean… makes server nonexistent

Posted December 27, 2020 842 views
DNSInitial Server Setup

hi, i own a domain from bluehost. recently i set up digitalocean.

ive migrated wordpress correctly however the domain name seems to be a problem. when i type in the url directly… it says…

DNSPROBEFINISHED_NXDOMAIN meaning its non-existent, am i correct?

however on bluehost, i repointed the DNS names to digital ocean.

i have.....

Name Servers

while on digitalocean, my setup shows…

DNS records directs to

what am i doing wrong? i thought by creating the droplet with 1-click, the apache server is set up along with all the other configurables

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
1 answer

Hi there @starmandell,

As far as I can see your domain name does not have an A record.

You need to go to your DigitalOcean Control panel then go to your DNS zone for your domain name and add a new A record to point to your Droplet’s IP address.

Note that it could take up to a few hours for the DNS cache to clear over the Globe before you could see the changes. You can use this tool here to check your DNS records:

Let me know how it goes!

  • thanks for your reply.

    unfortunately, the website still isn’t displaying.
    shows my dns did populate correctly. and i have added some A records.

    my apache server is running when i type up localhost on my browser. it displays ‘it works!’

    but on my browser, when i visit it shows....
    an empty page with as the url instead of the domain name.

    what am i doing wrong? i am using mac, but my apache is running. did i need configure my apache a specific way? the commands for ubuntu don’t work for me.... i did the one click for wordpress from the droplet install. does it not configure it?

    • Hi there 👋,

      The DNS problem seems to be fixed now which is a good improvement!

      The problem at the moment is that your WordPress site and home URLs are set to your server IP address rather than the domain name itself.

      You need to change that so that it matches the domain name that you want to use for that website.

      If you are going to be hosting your website on the server, you would not really need to have it running on your localhost directly.