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
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.