Re: named not answer on external query

2013-01-17 Thread lilit-aibolit
On 01/17/2013 04:05 PM, Michael Lambert wrote: On 17 Jan 2013, at 06:44, lilit-aibolit wrote: On 01/17/2013 11:27 AM, Vadim Zhukov wrote: At first, find where the flow gets stopped: enable debug logging on resolver and add "match log (matches) to port 53" rule as first one in your firewall. T

Re: named not answer on external query

2013-01-17 Thread Michael Lambert
On 17 Jan 2013, at 06:44, lilit-aibolit wrote: > On 01/17/2013 11:27 AM, Vadim Zhukov wrote: >> >> At first, find where the flow gets stopped: enable debug logging on resolver >> and add "match log (matches) to port 53" rule as first one in your firewall. >> Then probably you'll see the problem

Re: named not answer on external query

2013-01-17 Thread lilit-aibolit
On 01/17/2013 11:27 AM, Vadim Zhukov wrote: At first, find where the flow gets stopped: enable debug logging on resolver and add "match log (matches) to port 53" rule as first one in your firewall. Then probably you'll see the problem yourself. Oh, and please, if you get "no packets seen" pr

Re: named not answer on external query

2013-01-17 Thread Vadim Zhukov
17.01.2013 12:31 пользователь "lilit-aibolit" написал: > > This is weird trouble. Years ago I did authoritative server on openbsd 4.x and it's just works > for both - local network and queries from Internet. > But now it doesn't. I know - this is my issue, please help to resolve

named not answer on external query

2013-01-17 Thread lilit-aibolit
This is weird trouble. Years ago I did authoritative server on openbsd 4.x and it's just works for both - local network and queries from Internet. But now it doesn't. I know - this is my issue, please help to resolve. ###named.conf### // $OpenBSD: named-simple.conf,v 1.10 2009/11/02 21:12:56 jako