NXRRSET

[Thilanka Samarasekera]

--===============2067235999419351576==
Content-Type: multipart/alternative; boundary=00163662e657382c8504693f8259

--00163662e657382c8504693f8259
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello,

I am running BIND version 9.2.3 on a Solaris 9 box. Every now and then I
will see the following in my DNS cache:

domain.com. 458 \-AAAA ;-$NXRRSET

If I force a MX record lookup it does get the correct MX records for "
domain.com". The explanation I have for "NXRRSET" is "Its the number od
queries the name server handled that resulted in responses saying that the
type of record the querier requested didn't exist for the domain name it
specified". If do a MX record look for "domain.com" it does get the correct
entries and caches it for the specified TTL. My question is how do I go
about identifying what's causing my BIND server to cache a query with the
flag "NXRRSET" ?

Thank you in advance

--00163662e657382c8504693f8259
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello,</div>
<div>=A0</div>
<div>I am running BIND version 9.2.3 on a Solaris 9 box. Every now and then=
I will see the following in my DNS cache:</div>
<div>=A0</div>
<div><a href=3D"http://domain.com">domain.com</a>.=A0=A0=A0=A0=A0=A0 458=A0=
=A0=A0=A0 \-AAAA=A0 ;-$NXRRSET</div>
<div>=A0</div>
<div>If I force a MX record lookup it does get the correct MX records for &=
quot;<a href=3D"http://domain.com">domain.com</a>&quot;. The explanation I =
have for &quot;NXRRSET&quot; is &quot;Its the number od queries the name se=
rver handled that resulted in responses saying that the type of record the =
querier requested didn&#39;t exist for the domain name it specified&quot;. =
If do a MX record look for &quot;<a href=3D"http://domain.com">domain.com</=
a>&quot; it does get the correct entries and caches it for the specified TT=
L. My question is how do I go about identifying what&#39;s causing my BIND =
server to cache a query with the flag &quot;NXRRSET&quot; ?</div>

<div>=A0</div>
<div>Thank you in advance</div>

--00163662e657382c8504693f8259--

--===============2067235999419351576==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--===============2067235999419351576==--

[Chris Buxton]

On May 6, 2009, at 7:49 AM, Thilanka Samarasekera wrote:
> Hello,
>
> I am running BIND version 9.2.3 on a Solaris 9 box. Every now and
> then I will see the following in my DNS cache:
>
> domain.com. 458 \-AAAA ;-$NXRRSET
>
> If I force a MX record lookup it does get the correct MX records for
> "domain.com". The explanation I have for "NXRRSET" is "Its the
> number od queries the name server handled that resulted in responses
> saying that the type of record the querier requested didn't exist
> for the domain name it specified". If do a MX record look for
> "domain.com" it does get the correct entries and caches it for the
> specified TTL. My question is how do I go about identifying what's
> causing my BIND server to cache a query with the flag "NXRRSET" ?

The query getting the negative response here is for an AAAA record
named domain.com. For example, there might be:

example.com. MX 10 mx.example.com.
mx.example.com. A 192.0.2.1

Your cache might then end up with an NXRRSET (no such resource record
set) for mx.example.com/IN/AAAA, because the mail server is looking
for IPv6 addresses for the mail server.

Chris Buxton
Professional Services
Men & Mice