Re: erros in logs

2012-05-11 Thread Eivind Olsen
Ben wrote: > Hi, > > Currently we using ipv4 network for our customers and all.By the way, we > do not block any ipv6 , so why we got ipv6 resolution as network > unreachable in logs? BIND believes your OS has IPv6 and tries to use it. One option for disabling use of IPv6 in BIND is to tell BIND

Re: erros in logs

2012-05-11 Thread Ben
Hi, Currently we using ipv4 network for our customers and all.By the way, we do not block any ipv6 , so why we got ipv6 resolution as network unreachable in logs? On 10/05/12 09:47, Ben wrote: Hi, I just enable bind as caching name server and when watching logs i got below erros. It loo

Re: erros in logs

2012-05-10 Thread Phil Mayers
On 10/05/12 09:47, Ben wrote: Hi, I just enable bind as caching name server and when watching logs i got below erros. It looks like you have broken IPv6 connectivity - your machine believes it has an IPv6 address and possibly a default route, but it doesn't work. Check your networking confi

Re: erros in logs

2012-05-10 Thread Niall O'Reilly
On 10 May 2012, at 09:47, Ben wrote: > I just enable bind as caching name server and when watching logs i got below > erros. You seem to be noticing 3 kinds of error. "Network unreachable" messages refer only to IPv6 destinations. Perhaps you have IPv6 enabled on the sy

erros in logs

2012-05-10 Thread Ben
Hi, I just enable bind as caching name server and when watching logs i got below erros. error (network unreachable) resolving 'www.indiaresultsalert.com//IN': 2001:503:a83e::2:30#53 error (network unreachable) resolving 'ns-797.awsdns-35.net/A/IN': 2001:503:231d::2:30#53 error (network