Bind does not reply with "no such name" to A query

[Kevin Darcy]

On 11/9/2011 6:18 AM, Gaurav Kansal wrote:
> Dear Sven,
>
>
>
> Client queries a name for Both A and AAAA records.
>
> Now, the thing is NAME exist but either A or AAAA doesn't exist for this.
> Then how can a server reply that "no such name"??????
>
>
>
>
>
> Thanks and Regards,
>
> Gaurav Kansal
>
> 9910118448
>
>
>
>
>
> From: bind-users-bounces+gaurav.kansal=nic.in at lists.isc.org
> [mailto:bind-users-bounces+gaurav.kansal=nic.in at lists.isc.org] On Behalf Of
> Beisiegel, Sven
> Sent: Wednesday, 09 November, 2011 3:04 PM
> To: bind-users at lists.isc.org
> Subject: Bind does not reply with "no such name" to A query
>
> at
>
>
> Hi everyone,
> I tried to find a solution to this using Google, but I failed. I'm wondering
> if this is expected behavior of bind9 or if this is configurable.
>
> I have a domain configured and my server is the authoritative name server
> for this domain.
> My server is reachable via IPv4 and IPv6 address.
> 2 records are configured like this:
>
>
>
> dls-koe.gvs.local.                 2h     A      192.168.100.251
>
> dls-koe-v6.gvs.local.              2h     AAAA   2001:4dd0:f9c0:100::251
>
>
>
> I have clients that are running with IPv4 and IPv6 address at the same time
> and are configured with one of the FQDNs above. When the client is sending a
> query for one of the names, it directly sends an A and AAAA query.
> Now for example: The client sends an A query for "dls-koe-v6.gvs.local",
> which is only configured as AAAA record in the server. I now would expect
> the server to reply with "no such name", but it doesn't.
> Other example: The client sends an AAAA query for "dls-koe.gvs.local", which
> is only configured as A record in the server. Same result.
>
> My question is: Why is bind not replying with "no such name" in this case?
> Is this expected behavior? Maybe a configuration issue?
>
Guys, please read these questions more carefully.

These are *different* names. dls-koe.gvs.local versus 
dls-koe-v6.gvs.local. The original poster's question is a valid one. 
Based on the information so far, he should be getting NXDOMAIN responses.

I suspect these names are "non-terminal" (i.e. something is defined 
underneath them in the hierarchy, e.g. foo.dls-koe.gvs.local) and that's 
why he's getting NODATA instead of NXDOMAIN.

Another possibility is that nslookup is doing some searchlisting and 
misreporting "no such name". It tends to do that.

                                                                         
                                                                         
                                                 - Kevin

P.S. To the original poster: you might want to avoid the TLD .local for 
regular DNS, since it's supposedly reserved for mDNS.