On 5/14/21 1:14 PM, Jack Craig wrote:
Hi folks
With help from this list I recently updated my DNS configuration to provide for a primary and secondary DNS server where the primary DNS server is my host inside my domain and the secondary server is provided by AT&T
I discovered that the secondary server on file with my registrar was wrong so I got the right data and they claim to have created a glue record but I'm still getting that host is not responding
*primary dns ws.linuxlighthouse.com http://ws.linuxlighthouse.com* *Secondary server ns2.swbell.net http://ns2.swbell.net*
would some kind soul direct me to a coherent glue (or duct tape) record test?
also, given some domain name how do you know which top level domain name servers should be the first set that you query to locate your domain in question??
pick a random root-server: ( [a..m] means a through m )
dig @[a..m].root-servers.net. linuxlighthouse.com.
will give you the servers for com.
which are [a..m].gtld-servers.net.
dig @[a..m].gtld-servers.net. linuxlighthouse.com.
;linuxlighthouse.com. IN A
;; AUTHORITY SECTION: linuxlighthouse.com. 172800 IN NS ns2.swbell.net. linuxlighthouse.com. 172800 IN NS ws.linuxlighthouse.com.
;; ADDITIONAL SECTION: ws.linuxlighthouse.com. 172800 IN A 108.220.213.121
The A record points to your primary.
If you need to find out about your IP address you use the ARPA servers
dig @[a..f].in-addr-servers.arpa. 121.213.220.108.in-addr.arpa.
will give you the servers for 108.in-addr.arpa.
dig @[ruxyz].arin.net. 121.213.220.108.in-addr.arpa.
gives you bell nameservers. Now that you are there you must search for your PTR record.
;121.213.220.108.in-addr.arpa. IN PTR
;; ANSWER SECTION: 121.213.220.108.in-addr.arpa. 7200 IN PTR ws.linuxlighthouse.com.
;; AUTHORITY SECTION: 213.220.108.in-addr.arpa. 7200 IN NS ns2.swbell.net. 213.220.108.in-addr.arpa. 7200 IN NS ns3.sbcglobal.net. 213.220.108.in-addr.arpa. 7200 IN NS ns1.swbell.net.