Ambiguous def of multiple CNAME

Christine.Tran at Christine.Tran at
Tue Nov 30 23:00:26 UTC 1999

>Strange, but this works fine for me. I defined "" in a bogus >version of the zone, as an alias to When I queried >it, it translated the CNAME, then used the forwarder to fetch the A record. >This is just using a generic type of >configuration. Is yours different somehow?

My config is plain-jane forward-if-you-dont-know-it.  My internal server is auth for, say,  The rest of this is real.    IN      CNAME

Here's the debug of me nslookup RIGHT ON THE INTERNAL NAMESERVER:

req: nlookup( id 13204 type=1 class=1
req: found '' as '' (cname=0)
req: nlookup( id 13204 type=1 class=1
req: found '' as '' (cname=1)
evSetTimer(ctx 0x15f590, func 0x39ed4, uap 0, due 943984296.000000000, inter 0.0
forw: forw -> [].53 ds=4 nsid=3597 id=8238 5ms retry 8sec
Response (USER NORMAL -) nsid=3597 id=13204
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3597
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;;, type = A, class = IN             21h53m32s IN NS             21h53m32s IN NS         23h36m45s IN A          23h36m45s IN A
resend(addr=1 n=0) -> [].53 ds=4 nsid=3597 id=13204 21ms

So you see how now I try to contact to get the A RR, and then times out.  What's interesting is the line
;;, type = A, class = IN

Why do I have an A RR returned to me, but no IP??


More information about the bind-users mailing list