site not resolving, what's wrong with A Records ?

January 24, 2013 4.3k views
turchetto
By:
turchetto
Is it normal that, after pointing ns from godaddy to digitalocean, subdomain are resolving but main site isn't resolving at all ? Here's my raw config. Seems anything wrong. Maybe it's my fault (i'm working from 12 hours) but according raw bind i don't see errors. $TTL 7200 @ IN SOA ns1.digitalocean.com. hostmaster.mysite.net. ( 1359008096 ; last update: 2013-01-24 06:14:56 UTC 3600 ; refresh 900 ; retry 1209600 ; expire 10800 ; 3 hours ttl ) IN NS ns1.digitalocean.com. NS ns2.digitalocean.com. NS ns3.digitalocean.com. MX 1 ASPMX.L.GOOGLE.COM. MX 5 ALT1.ASPMX.L.GOOGLE.COM. MX 5 ALT2.ASPMX.L.GOOGLE.COM. MX 10 ASPMX2.GOOGLEMAIL.COM. MX 10 ASPMX3.GOOGLEMAIL.COM. mysite.net IN A 111.111.111.111 www.mysite.net CNAME mysite.net. download IN A 111.111.111.111 www.download IN A 111.111.111.111 host IN A 111.111.111.111
Log In to Comment
3 Answers
moisey MOD January 24, 2013
You are missing the default record which is automatically created when you specify an IP for the domain during the domain create.

Add an "A" record with the following:
"@" -> "111.111.111.111"

And you should be all set.

Also if you add another domain or a test domain you will see that this record is automatically generated and pointed to the IP you specify.
Reply
turchetto January 24, 2013
Upsss, my fault.... Thank you for your valuable feedback :)
Reply
turchetto January 24, 2013
My bad, i had to sleep instead configuring servers.: www CNAME mysite.net.

BTW, Thank you another time for your valuable feedback :)
Reply
Have another answer? Share your knowledge.