Am 26.12.2012 um 23:31 schrieb Mark Andrews :
> * the record to be removed was not there
> * the record to be aded was already there
>
> This means that the two versions of the zone have become unsyncronized.
I did some more tests with another zone. Not sure BIND works as intended there:
- zone
Am 26.12.2012 um 23:31 schrieb Mark Andrews :
> What it is complaining about is that when the change you just applied to the
> unsigned version of the zone is applied to the signed version it
> found one of:
>
> * the record to be removed was not there
> * the record to be aded was already there
In message <0fac2f01-3384-45da-8ad9-738fb175b...@leuxner.net>, Thomas Leuxner
writes:
> Hi,
>
> I'm having the problem that after rolling a dynamic update on one of the
> zones - a newly signed zone - the signed zone does not get updated, but
> mocks about the serial being 'not exact'.
The ab
Hi,
I'm having the problem that after rolling a dynamic update on one of the zones
- a newly signed zone - the signed zone does not get updated, but mocks about
the serial being 'not exact'.
Dec 26 07:39:26 spectre named[23831]: client 188.138.3.243#16192/key
tlx.leuxner.net: signer "tlx.leuxn
4 matches
Mail list logo