When using dig ns/soa +norec command, information for the
respective is returned and cached in the my-nets view.

Benu

; <<>> DiG 9.2.3 <<>> soa rescue911design.com @192.168.2.2
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 46695
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;rescue911design.com. IN SOA

;; Query time: 2 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:33:02 2004
;; MSG SIZE rcvd: 37


; <<>> DiG 9.2.3 <<>> soa rescue911design.com @127.0.0.1
;; global options: printcmd
;; connection timed out; no servers could be reached

; <<>> DiG 9.2.3 <<>> soa rescue911design.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 22504
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;rescue911design.com. IN SOA

;; Query time: 2 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:33:53 2004
;; MSG SIZE rcvd: 37


; <<>> DiG 9.2.3 <<>> soa benu.widge.net @192.168.2.2
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 55643
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;benu.widge.net. IN SOA

;; Query time: 20 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:34:06 2004
;; MSG SIZE rcvd: 32


; <<>> DiG 9.2.3 <<>> soa benu.widge.net @127.0.0.1
;; global options: printcmd
;; connection timed out; no servers could be reached

; <<>> DiG 9.2.3 <<>> soa blkdiamonds.lan
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53132
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;blkdiamonds.lan. IN SOA

;; ANSWER SECTION:
blkdiamonds.lan. 259200 IN SOA ns1.blkdiamonds.lan.
root.blkdiamonds.lan. 200410103 28800 7200 2419200 86400

;; AUTHORITY SECTION:
blkdiamonds.lan. 259200 IN NS ns1.blkdiamonds.lan.

;; ADDITIONAL SECTION:
ns1.blkdiamonds.lan. 259200 IN A 192.168.2.2

;; Query time: 2 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:35:08 2004
;; MSG SIZE rcvd: 108


; <<>> DiG 9.2.3 <<>> ns blkdiamonds.lan
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59448
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;blkdiamonds.lan. IN NS

;; ANSWER SECTION:
blkdiamonds.lan. 259200 IN NS ns1.blkdiamonds.lan.

;; ADDITIONAL SECTION:
ns1.blkdiamonds.lan. 259200 IN A 192.168.2.2

;; Query time: 2 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:35:20 2004
;; MSG SIZE rcvd: 67

Host www.sendate.gov not found: 2(SERVFAIL)

; <<>> DiG 9.2.3 <<>> ns sendate.gov +norec
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64062
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 7, ADDITIONAL: 0

;; QUESTION SECTION:
;sendate.gov. IN NS

;; AUTHORITY SECTION:
gov. 102904 IN NS B.GOV.ZONEEDIT.COM.
gov. 102904 IN NS C.GOV.ZONEEDIT.COM.
gov. 102904 IN NS D.GOV.ZONEEDIT.COM.
gov. 102904 IN NS E.GOV.ZONEEDIT.COM.
gov. 102904 IN NS F.GOV.ZONEEDIT.COM.
gov. 102904 IN NS G.GOV.ZONEEDIT.COM.
gov. 102904 IN NS A.GOV.ZONEEDIT.COM.

;; Query time: 2 msec
;; SERVER: 192.168.2.2#53(192.168.2.2)
;; WHEN: Tue Oct 12 07:45:32 2004
;; MSG SIZE rcvd: 157



Barry Margolin wrote on 10/11/2004, 6:31 PM:

> Could you provide some example queries that fail?
>
> If you try to look up something in rescue911design.com or benu.widge.net
> from your homelan, it won't use the data from the zone files, it should
> forward to the ISP nameservers. This is because you only list these
> zones in the external-nets view.