Re: cnames stop resolving

HERE's an example of the non-resolving dig command:

; <<>> DiG 9.2.3 <<>> @10.99.9.6 ext-host.domain.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;ext-host.domain.net. IN A

;; ANSWER SECTION:
ext-host.domain.net. 3600 IN CNAME
int-hostname.internal-domain.com.

;; AUTHORITY SECTION:
internal-domain.com. 86400 IN SOA
dns23.register.com. root.register.com. 200007275 10800 3600 604800
86400

;; Query time: 46 msec
;; SERVER: 10.99.9.6#53(10.99.9.6)
;; WHEN: Fri May 26 09:22:56 2006
;; MSG SIZE rcvd: 150

HERE'S THE EXPECTED OUTPUT

; <<>> DiG 9.2.3 <<>> @10.99.9.8 ext-host.domain.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ext-host.domain.net. IN A

;; ANSWER SECTION:
ext-host.domain.net. 3068 IN CNAME
int-hostname.internal-domain.com.
int-hostname.internal-domain.com. 900 IN A 10.99.9.21

;; Query time: 0 msec
;; SERVER: 10.99.9.8#53(10.99.9.8)
;; WHEN: Fri May 26 09:23:15 2006
;; MSG SIZE rcvd: 9

as you can see on the first query, i get the nxdomain problem...

.

Relevant Pages
Loading