: 83
Does the SERVER line indicate it's trying to get to the local instance via
IPV6 or is this just standard notation? (This is an IPV4 only environment).
--
Konstantin Stefanov
___
Please visit https://lists.isc.org/mailman/listinfo/bind-
Hi,
I think you can achieve the same effect with dig, but it requires some
preparations.
First, enable zone transfers for your slave zone from 127.0.0.1: add
allow-transfer {127.0.0.1;}; to your slave zone definition (or add
127.0.0.1 there if you already have allow-transfer).
Then you can
Requirement to have 2 synced definitions in 2 different places leads to
bugs.
>
>>> the only other way is stop using views...
>
--
Konstantin Stefanov,
Research Computing Center
M.V Lomonosov Moscow State University
___
Please visit h
t;>> before upgrade.
>>>
>>> I mean, the "in-view" definitions...
>
> On 18.03.15 13:10, Konstantin Stefanov wrote:
>> So now I have to have two definitions for every slave zone in different
>> files. Well, it is the thing I did, but I do no
for slave zone
caches, or have 'in-view' directive. So simply copying does not work,
otherwise 'include' would work fine.
> -Original Message-
> From: bind-users-boun...@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Konstantin Stefanov
&g
On 18.03.2015 16:55, Steven Carr wrote:
> On 18 March 2015 at 13:30, Konstantin Stefanov wrote:
>> It isn't. But maintaining one file is easier. And having to maintain two
>> after five years everything worked fine with one is annoying.
>
> This highlights the need for
On 18.03.2015 17:18, Matus UHLAR - fantomas wrote:
> rOn 18.03.15 17:10, Konstantin Stefanov wrote:
>> The issue is that named started to detect it since, if I'm not mistaken,
>> 9.7. It happened because such config was leading to bugs, but instead of
>> fixing the b
termine the answer.
I think ARM is quite explicit that directory is only allowed in
'options' clause. But to be sure I tried to put 'directory' into view
and got an error
unknown option 'directory'
> The second way definitely does NOT exist, and that would be to
On 18.03.2015 18:10, wbr...@e1b.org wrote:
> From: Konstantin Stefanov
>
>> The issue is that named started to detect it since, if I'm not mistaken,
>> 9.7. It happened because such config was leading to bugs, but instead of
>> fixing the bugs, the whole feature was
On 18.03.2015 18:37, Reindl Harald wrote:
>
> Am 18.03.2015 um 16:31 schrieb Konstantin Stefanov:
>> I wrote earlier and may repeat again. The feature for me is not using
>> the same file, the feature is having a clear and maitainable config. In
>> this case it means to h
On 18.03.2015 20:10, /dev/rob0 wrote:
> On Wed, Mar 18, 2015 at 06:11:56PM +0300, Konstantin Stefanov wrote:
>> On 18.03.2015 17:41, /dev/rob0 wrote:
>>> On Wed, Mar 18, 2015 at 11:48:40AM +0300, Constantin Stefanov wrote:
>>>> I see why it may lead to probl
host.48466: Flags [F.], seq 363, ack
> 321, win 1433, options [nop,nop,TS val 196636465 ecr 196636281], length 0
> 21:23:37.829288 IP localhost.48466 > localhost.953: Flags [.], ack 364, win
> 1433, options [nop,nop,TS val 196636465 ecr 196636465], length 0
>
> Is there a w
rlier
versions? Try man -a named.conf and see if there are other vresions of
man page.
By default bind99 port uses /usr/local/etc/namedb, but it used to have
REPLACE_BASE option, which instructed it to use /etc/namedb, so you may
check it.
--
Konstantin Stefanov,
Research Computing Center
M.V Lomonos
13 matches
Mail list logo
