Glenn Vidad wrote:
> got it.... it was staring right at me... here's the info as you
> suggested...
> just noticed "ANSWER: 0"
>
> [gvidad at renegade gvidad]$ dig a @ns2.myersinternet.com www.cisco.com
>
> ; <<>> DiG 9.2.0 <<>> a @ns2.myersinternet.com www.cisco.com
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23803
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;www.cisco.com. IN A
>
> ;; AUTHORITY SECTION:
> cisco.com. 169439 IN NS NS1.cisco.com.
> cisco.com. 169439 IN NS NS2.cisco.com.
>
> ;; ADDITIONAL SECTION:
> NS1.cisco.com. 169439 IN A 128.107.241.185
> NS2.cisco.com. 169439 IN A 192.135.250.69
>
> ;; Query time: 48 msec
> ;; SERVER: 216.34.18.4#53(ns2.myersinternet.com)
> ;; WHEN: Wed Nov 13 16:09:38 2002
> ;; MSG SIZE rcvd: 99
That's perfect. Notice that the response you got back wasn't the
address of www.cisco.com; it was a referral to the cisco.com
name servers. More importantly, notice that the "rd" bit was set
in the flags ("recursion desired," indicating a recursive query),
but the "ra" bit wasn't ("recursion available").
So that demonstrates that, from wherever you ran dig,
recursion wasn't available.
cricket
Men & Mice
DNS Software, Training and Consulting
www.menandmice.com
The DNS and BIND Cookbook, available now!
http://www.oreilly.com/catalog/dnsbindckbk/