LinuxQuestions.org - [SOLVED] taking control of zone from godaddy registered domain

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - taking control of zone from godaddy registered domain (https://www.linuxquestions.org/questions/linux-server-73/taking-control-of-zone-from-godaddy-registered-domain-4175577119/)

taking control of zone from godaddy registered domain

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?

I have just realised that my second query was an error. I was querying a different non-existent domain. Now, even though I still don't receive any answers from example.com, or www.example.com, or mail.example.com, if I try using dig, then I get the line defined in my own zone:

example.com. 1450 IN SOA ns1.example.com. admin.example.com. 2016041001 12800 15 86400 12800
So that should be fine, but my queries are left answered. Is this simply a matter of time?

Quote:

Originally Posted by vincix (Post 5529036)

What happens if you query directly your dns for these hosts? E.g:

Code:

dig example.com @ns1.example.com

Code:

for i in ns1_ip ; do dig @$i example.com +short ; done

will show you the A Record assigned on the sole nameserver, (ns1.example.com).

FWIW: It seems you did everything correctly at GD.
Same process I used to edit nameserver A records today on 4 domains.

Hit save, wait < ~5m and bingo.
The splash says "up to 48 hours, blah-lie blah-lie"

Quote:

Originally Posted by Habitual (Post 5529487)

Code:

for i in ns1_ip ; do dig @$i example.com +short ; done

Indeed, all I needed was time. It's working fine now.

Thanks

Quote:

Originally Posted by vincix (Post 5529548)

Indeed, all I needed was time. It's working fine now.

Thanks

I'm waiting on my last 2 domains now...
Glad it worked out for you.