Quote:
Originally Posted by smallpond
For you to run a nameserver for *.yourdomain.com., the next level up needs to have an NS record that points to your nameserver. What do you get from:
Code:
dig -t NS yourdomain.com
|
I believe that's all set up correctly.
Results of dig -t NS mydomain.net:
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> -t ns mydomain.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1052
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;mydomain.net. IN NS
;; ANSWER SECTION:
mydomain.net. 300 IN NS mydomain.net.
;; ADDITIONAL SECTION:
mydomain.net. 300 IN A 73.102.xxx.xxx
;; Query time: 11 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 22 14:48:18 2016
;; MSG SIZE rcvd: 66
Note: This is from inside the PI. Can't dig anything outside. Connection times out.