On 03/05/2021 04:56, Doug H. wrote:
That says that ws.linuxlighthouse.com is the one and only name server for the domain. Whereas whois shows the more normal 2 minimum:
whois LINUXLIGHTHOUSE.COM | grep ^Name
Name Server: WS.LINUXLIGHTHOUSE.COM Name Server: NS3.ATTDNS.COM
So, even if you let NS3.ATTDNS.COM pull the zone from you it might not work correctly if they just use the zone you feed them without adding themselves to the mix with an NS record.
Good point. I'd forgotten about NS3.ATTDNS.COM.
Oddly, ns3.attdns.com doesn't return any ns records for the domain while google does.
[root@meimei proc]# dig @ns3.attdns.com linuxlighthouse.com
; <<>> DiG 9.16.11-RedHat-9.16.11-5.fc34 <<>> @ns3.attdns.com linuxlighthouse.com ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 13291 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;linuxlighthouse.com. IN A
;; Query time: 194 msec ;; SERVER: 2001:1890:1c00:5323::c:3#53(2001:1890:1c00:5323::c:3) ;; WHEN: Mon May 03 05:39:19 CST 2021 ;; MSG SIZE rcvd: 48
[root@meimei proc]# dig @8.8.8.8 linuxlighthouse.com ns
; <<>> DiG 9.16.11-RedHat-9.16.11-5.fc34 <<>> @8.8.8.8 linuxlighthouse.com ns ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61405 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;linuxlighthouse.com. IN NS
;; ANSWER SECTION: linuxlighthouse.com. 21599 IN NS ws.linuxlighthouse.com.
;; Query time: 212 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon May 03 05:40:29 CST 2021 ;; MSG SIZE rcvd: 65