Behaviour of a recursive DNS server

[yjchu]

I seems that using html will cause problem in the mailing list, so I resend
the reply:
-------------------------------

I query the domain name "www.google.com.tw", and the query type is AAAA.

Actually, the DNS server I use is 168.95.1.1, which is the DNS server
provided by Hinet ISP in Taiwan.

Besides, I have double checked the DNS flag. Both the query and the DNS
server set the recursive flag..

Regards
Yann-Ju Chu

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf
Of JINMEI Tatuya / 神明達哉
Sent: Wednesday, June 11, 2008 2:38 AM
To: yjchu
Cc: bind-users at isc.org
Subject: Re: Behaviour of a recursive DNS server

At Tue, 10 Jun 2008 14:30:08 +0800,
"yjchu" <yjchui at cht.com.tw> wrote:

> I am trying IPv6 NAT-PT, so I wish my DNS server (my ISP DNS server) can
be
> purely recursive.
> 
> So, I send a recursive query, and my DNS server does reply recursively but
> with strange behaviors described as following:

> ----------------------
> 
> Sometimes, the DNS server will have two replies for single one query.
> 
> The first reply will only contain the CNAME but no A or AAAA record
> (address) information for the CNAME.
> 
> Then, the second reply has all the information, including CNAME and A/AAAA
> record information.

Can you provide specific domain names and query types that cause this
result?

> I have tried to build up my own DNS server using Bind 9.2.1 and make it
> support recursive reply.

I'm not sure if it's related to the issue, but I'd suggest you use a
more recent version.  9.2.1 is way too old and is basically not
supported any more.

> I find that sometimes, the reply of my DNS server just contains CNAME
record
> for my query name, no further information. (No second reply with address
> information).
> 
> However, from the sniffer, the recursive flag in DNS reply is set !!!!

This may be a typo, but in case you really looked at the reply, you
should rather look at the recursive (RD) flag of the *query*.

Finally, you cannot always assume that a response contains a complete
chain to the final answer.  You'll need to adapt your software (the
DNS client) so that it can handle an incomplete CNAME/DNAME chain
anyway.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.