Hi guys I have visited this topic several times before, but this time I think I have everything set up correctly. Including tighter security on my servers. And, hopefully, I just need a few pointers this time. OK this is the setup I have a registered domain Code: gregson.me.uk I also have a /29 block of IP addresses. Code: gregson.me.uk = 212.159.96.42 ns1.gregson.me.uk = 212.159.96.43 ns2.gregson.me.uk = 212.159.96.44 I have my glue records set with my domain provider pointing at the above records. All this has been discussed be for in several other threads. I have a multi ISP Config server setup I have created a DNS zone for gregson.me.uk but am not sure which IP address I should use in the DNS zone? I think it should be Code: 212.159.96.42 because that is the direct address of the actual domain. Also, will I also need “a” records in this zone for ns1 and ns2 as well as the 2 ns records? Many thanks in advance
The IP address where the domain name should point to, or in other words, the IP address of the web server that hosts the site gregson.me.uk Yes. The reason is that your NS records are subdomains of the same zone, in that special case, A-Records are needed for ns1 and ns2 as well.
Thanks till So to confirm the information I have I should not need anything with my domain registrar other than the name server entries. the "A" records should be created within the DNS zone on my server
yes. On your registrar's server, you have the glue records, but they do not replace the requirement that you must add the A-records on your server too.
One last thing... If I use the dig command to query my server I can specify the dns server to get the information. so if I use Code: dig @212.159.96.43 gregson.me.uk any Regardless of the propagation has completed or not I should get a result from the specified server Is this correct?
If you want to test if the dns server on your server is working fine already, use this command: dig @localhost gregson.me.uk the command must be run on the shell of your server and returns the IP address of the zone if successful.
You missed adding a dot at the end of the ns1 and ns2 A-Records. Any fully qualified domain name in DNS must end with a dot. So you can either use "ns1" which is the short form without a dot or "ns1.gregson.me.uk." which ends with a dot, this is the long notation.
Yes Taleman I have and thought I had followed it correctly but obviously missed the dot at the end of the "A" records for my NS servers
OK all seems to be working apart from one thing I don't understand from the dig report in the additional section Code: ;; ADDITIONAL SECTION: mail.gregson.me.uk. 3042 IN A 212.159.96.42 ns1.gregson.me.uk. 158711 IN A 212.159.96.42 ns2.gregson.me.uk. 158711 IN A 212.159.60.78 Am I right in thinking that the two NS parts of this section should show the public IP addresses for my ns1 and ns2 servers? and if that is the case could my Domain provider have got my glue records wrong?
This looks good to me. But verify the IP's you set are correct and the same at your registrar and your nameservers, and the firewall is opened on port 53.
How does this site get the information? I think my registrar has a mix of my old IPs and the ones I gave them.
