I've bought a godaddy domain and I have changed (or tried to) the nameservers to my nameserver, which is bind running on a Centos 7.
For whomever is familiar with the Godaddy interface, I added two hostnames (ns1 and ns2.example.com) which I associated with my server's ip address, and then I changed the nameservers from the default ones (provided by Godaddy - ns.domaincontrol.com or thereabouts) to ns1.example.com and ns2.example.com. I'm currently not using the latter.
I configured my zone, as follows:
Code:
$ORIGIN example.com.
$TTL 86400
@ IN SOA ns1.example.com. admin.example.com. (
2016041002;
12800;
15;
86400;
12800;
)
IN NS ns1.example.com.
IN MX 10 mail.example.com.
ns1 IN A 1.2.3.4
IN A 1.2.3.4
www IN A 1.2.3.4
mail IN A 1.2.3.4
test IN A 1.2.3.4
The weird thing that is happening now is that example.com isn't associated with my public ip, and neither is test.example.com. However, mail and www did work for some time - I could use nslookup, dig, etc. and they were associated with my server's ip address.
So I couldn't figure out why example.com didn't work. When I tried using dig example.com, a line similar to this showed up:
example.com. IN SOA ns40.domaincontrol.com etc.
Now when I use dig, I get the following line:
com. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1460315487 1800 900 604800 86400
Now, mail, www don't work anymore either. So the association might have been created only for a short timespan and then the information was transferred to this
a.gtld-servers.net.
I am aware that not enough time might have passed, but I'm not sure if this is the case. So I'm trying to make heads or tails of the whole thing.
Any suggestions?