Re: Error logs in bind resolving

2014-01-02 Thread Chris Buxton
On Dec 31, 2013, at 11:25 PM, Gaurav Kansal wrote: > Thanks Chris for your useful comments. > > On Dec 30, 2013, at 9:46 PM, Gaurav Kansal wrote: >>> I am getting the error message for lot of domains. >>> >>> Log of error entries are attached. >>> >> All the ones I checked were caused by

RE: Error logs in bind resolving

2013-12-31 Thread Gaurav Kansal
Thanks Chris for your useful comments. On Dec 30, 2013, at 9:46 PM, Gaurav Kansal wrote: I am getting the error message for lot of domains. Log of error entries are attached. All the ones I checked were caused by broken implementations. Is this a broken implementation of IPv6 or some

Re: Error logs in bind resolving

2013-12-31 Thread Chris Buxton
On Dec 30, 2013, at 9:46 PM, Gaurav Kansal wrote: > I am getting the error message for lot of domains. > > Log of error entries are attached. All the ones I checked were caused by broken implementations. > Is it possible to configure bind so that error message should not be > generated in log

RE: Error logs in bind resolving

2013-12-30 Thread Gaurav Kansal
: Chris Buxton [mailto:cli...@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.kan...@nic.in> gaurav.kan...@nic.in> wrote: > Dear All

Re: Error logs in bind resolving

2013-12-30 Thread Chris Buxton
On Dec 30, 2013, at 2:29 AM, Gaurav Kansal 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 w

Error logs in bind resolving

2013-12-30 Thread Gaurav Kansal
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.