Error logs in bind resolving

[Gaurav Kansal]

Hi Chris,

 

Thanks for your response.

I am getting the error message for lot of domains.

 

Log of error entries are attached.

 

Is it possible to configure bind so that error message should not be
generated in logs file.

 

 

Regards,

Gaurav Kansal

 

 

-----Original Message-----
From: Chris Buxton [mailto:clists at buxtonfamily.us] 
Sent: Monday, December 30, 2013 11:53 PM
To: Gaurav Kansal
Cc: BIND Users
Subject: Re: Error logs in bind resolving

 

On Dec 30, 2013, at 2:29 AM, Gaurav Kansal < <mailto:gaurav.kansal at nic.in>
gaurav.kansal at nic.in> wrote:

 

> Dear All,

>  

> In my bind server logs, I am getting too much error logs of below
mentioned type.

> Can anyone pl. explain me why I am getting these logs and how to get rid
of those.

>  

> Although when I am doing dig for the domain (for which I am getting the
error), I am getting the valid output.

>  

> Thanks.

>  

> Dec 30 15:54:18 IPV6-NKN-DNS named[13123]: error (FORMERR) resolving 

> 'ib.sin1.geoadnxs.com/AAAA/IN': 64.208.141.10#53

 

I see an incorrect negative response. Could this be the problem? Here is the
end of a dig trace:

 

geoadnxs.com.                 172800  IN           NS
01.auth.nym1.appnexus.net.

geoadnxs.com.                 172800  IN           NS
01.auth.nym2.appnexus.net.

geoadnxs.com.                 172800  IN           NS
01.auth.lax1.appnexus.net.

geoadnxs.com.                 172800  IN           NS
01.auth.ams1.appnexus.net.

;; Received 222 bytes from 192.33.14.30#53(192.33.14.30) in 123 ms

 

sin1.geoadnxs.com.        86400    IN           NS
ns2.apac.gslb-ns.net.

sin1.geoadnxs.com.        86400    IN           NS
ns1.apac.gslb-ns.net.

;; Received 122 bytes from 68.67.133.169#53(68.67.133.169) in 67 ms

 

geoadnxs.com.                 30           IN           SOA
ns1.gslb.com. support.appnexus.net. 1 86400 30 86400 30

;; Received 103 bytes from 64.208.141.10#53(64.208.141.10) in 187 ms
_______________________________

 

My resolving name server complains as follows:

 

Dec 30 10:19:45 ubuntu named[1299]: DNS format error from 64.208.141.10#53
resolving ib.sin1.geoadnxs.com/AAAA for client ::1#60014: invalid response
Dec 30 10:19:45 ubuntu named[1299]: error (FORMERR) resolving
'ib.sin1.geoadnxs.com/AAAA/IN': 64.208.141.10#53 Dec 30 10:19:45 ubuntu
named[1299]: DNS format error from 64.208.141.11#53 resolving
ib.sin1.geoadnxs.com/AAAA for client ::1#60014: invalid response Dec 30
10:19:45 ubuntu named[1299]: error (FORMERR) resolving
'ib.sin1.geoadnxs.com/AAAA/IN': 64.208.141.11#53
_______________________________

 

I believe the problem is that when asked for an AAAA record, the load
balancer gives an otherwise-proper-looking negative response that claims to
be from the wrong zone.

 

Regards,

Chris Buxton

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20131231/118977bf/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: error code.txt
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20131231/118977bf/attachment-0001.txt>