Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
How to configure Bind9 to work with wildcard domains? Question Question
PTR *removal* only IP address - reverse DNS Question Question

Question

Server not found after configuring digitalocean dns

Posted October 12, 2016 5.2k views
UbuntuDNS

I’ve tried following this guide but it doesn’t work.
http://withr.me/add-domain-name-for-your-server-on-digitalocean/

I wanted to point cruzgsworks.space, a domain which i registered in godaddy, to my droplet 198.199.95.70

I’ve taken screenshots of my configurations (zonefiles, nameservers, etc) in godaddy and digitalocean and uploaded it in my Ubuntu droplet which already has an apache2 server.
http://198.199.95.70/images/

Is there something wrong with my current configuration or is there anything else that is missing?

Any help is greatly appreciated

Add a comment
jigsgisc
By:
jigsgisc

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
How to configure Bind9 to work with wildcard domains? Question Question
PTR *removal* only IP address - reverse DNS Question Question

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
mnordhoff October 12, 2016

Odd. I think you have everything set up correctly – or, at least, functionally – but it doesn’t work anyway. I’m not sure why.

The screenshots show and whois cruzgsworks.space confirms that you’ve set it to use DigitalOcean’s nameservers. However, the .space nameservers don’t return any (NS) records for the domain. My guess is that you just have to wait and it will start working within the next couple hours.

$ dig +norecurse cruzgsworks.space @b.nic.space.

; <<>> DiG 9.10.3-P4-Ubuntu <<>> +norecurse cruzgsworks.space @b.nic.space.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41607
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;cruzgsworks.space.             IN      A

;; AUTHORITY SECTION:
space.                  3600    IN      SOA     ns0.centralnic.net. hostmaster.centralnic.net. 3000224808 900 1800 6048000 3600

;; Query time: 1 msec
;; SERVER: 2a04:2b00:13cc::1:51#53(2a04:2b00:13cc::1:51)
;; WHEN: Wed Oct 12 02:18:26 UTC 2016
;; MSG SIZE  rcvd: 111

By the way, the CNAME and MX records you’ve created in GoDaddy’s DNS manager effectively do not exist, because you’ve configured the domain to use DigitalOcean’s DNS service. You should set the necessary records in DigitalOcean’s DNS manager, or switch the domain to use GoDaddy’s DNS somewhere in GoDaddy’s domain settings.

Reply Report
  • jigsgisc October 12, 2016

    I see. Thanks. I’ll try waiting it out for a day. Hopefully it resolves soon.

    On the GoDaddy’s DNS Zone File tab, is it okay if I remove all entries there right since - “I’ve configured the (cruzgsworks.space) domain to use DigitalOcean’s DNS service”?

    Reply Report
    • mnordhoff October 12, 2016

      Yes, you can remove all the GoDaddy DNS records – don’t remove the nameserver settings elsewhere in the manager – if you’re happy with DigitalOcean’s DNS setup. As i said before, the GoDaddy MX records and so forth didn’t exist in DigitalOcean’s DNS manager. If you want them to, you ought to fix that. Although it doesn’t have any bearing on whether or not you delete them at GoDaddy.

      Reply Report

Related

Looking for something else?

Ask a new question Search for more help