, because after
recreating the files in 9.14.9, everything is now working normally again.
Jukka
-Alkuperäinen viesti-
Lähettäjä: bind-users Puolesta Alessandro
Vesely
Lähetetty: 28. tammikuuta 2020 14:26
Vastaanottaja: bind-users@lists.isc.org
Aihe: Re: VL: DNSSEC zones not updated
ror..
>
> Jukka
>
> -Alkuperäinen viesti-
> Lähettäjä: Mark Andrews
> Lähetetty: 23. tammikuuta 2020 0:53
> Vastaanottaja: Jukka Pakkanen
> Kopio: bind-us...@isc.org; Browne, Stuart
> Aihe: Re: DNSSEC zones not updated
>
> On the master stop the server, re
Yes, that worked. Also had to delete the .jnl, to prevent the "not exact"
error..
Jukka
-Alkuperäinen viesti-
Lähettäjä: Mark Andrews
Lähetetty: 23. tammikuuta 2020 0:53
Vastaanottaja: Jukka Pakkanen
Kopio: bind-us...@isc.org; Browne, Stuart
Aihe: Re: DNSSEC zones not u
rom: Browne, Stuart
> Sent: Thursday, January 23, 2020 12:14:29 AM
> To: Jukka Pakkanen ; bind-us...@isc.org
>
> Subject: RE: DNSSEC zones not updated
>
> Sadly, no ideas other than a shared experience. It's not just the Windows
> release nor is it just the 9.14 series of r
i36>
From: Browne, Stuart
Sent: Thursday, January 23, 2020 12:14:29 AM
To: Jukka Pakkanen ; bind-us...@isc.org
Subject: RE: DNSSEC zones not updated
Sadly, no ideas other than a shared experience. It's not just the Windows
release nor is it just the 9.14 series of releases; we've
: Jukka Pakkanen; bind-us...@isc.org
Subject: VS: DNSSEC zones not updated
Anyone, any ideas?
Lähettäjä: bind-users
mailto:bind-users-boun...@lists.isc.org>>
Puolesta Jukka Pakkanen
Lähetetty: 22. tammikuuta 2020 13:30
Vastaanottaja: bind-us...@isc.org<mailto:bind-us...@isc.org>
Aihe:
Anyone, any ideas?
Lähettäjä: bind-users Puolesta Jukka Pakkanen
Lähetetty: 22. tammikuuta 2020 13:30
Vastaanottaja: bind-us...@isc.org
Aihe: Re: DNSSEC zones not updated
And we also get after a change and a reload the "secure_serial: not exact"
error, of course because the signed z
aka.ms/ghei36>
From: jukka.pakka...@qnet.fi
Sent: Wednesday, January 22, 2020 1:13:11 PM
To: Ondřej Surý
Cc: bind-us...@isc.org
Subject: Re: DNSSEC zones not updated
Yed we have quite several times by now when trying to find the culprit. Also
the whole win
On Wed, Jan 22, 2020 at 11:11:05AM +, Jukka Pakkanen wrote:
> zone "gemtrade.fi" {
> type master;
> file "named.gemtrade";
> inline-signing yes;
> auto-dnssec maintain;
> };
>
> $TTL 60
> @IN SOAns1.qnet.fi. helpdesk.qnet.fi. (
> 202001234 ; serial nu
ary 22, 2020 1:08:22 PM
To: Jukka Pakkanen
Cc: bind-us...@isc.org
Subject: Re: DNSSEC zones not updated
Hi,
did you try stopping BIND, removing journal files and then starting BIND again?
If the signed copy of the zone got corrupted in the memory, you might be
dumping the corrupted version on disk
Hi,
did you try stopping BIND, removing journal files and then starting BIND again?
If the signed copy of the zone got corrupted in the memory, you might be
dumping the corrupted version on disk again with `rndc reload`.
Ondrej
--
Ondřej Surý
ond...@isc.org
> On 22 Jan 2020, at 12:11, Jukka Pa
:56
To: Jukka Pakkanen
Cc: bind-us...@isc.org
Subject: Re: DNSSEC zones not updated
Just a basic question, are you querying the master or a slave. If a slave, it
could be the notify/transfer.
Thanks
Sten
On 22 Jan 2020, at 12.11, Jukka Pakkanen
mailto:jukka.pakka...@qnet.fi>> wrote:
Just a basic question, are you querying the master or a slave. If a slave, it
could be the notify/transfer.
Thanks
Sten
> On 22 Jan 2020, at 12.11, Jukka Pakkanen wrote:
>
>
> Running BIND 9.14.9 Windows. The zone data is not updated for some reason
> anymore, and same problem in all our
Running BIND 9.14.9 Windows. The zone data is not updated for some reason
anymore, and same problem in all our signed zones. Example "gemtrade.fi":
zone "gemtrade.fi" {
type master;
file "named.gemtrade";
inline-signing yes;
auto-dnssec maintain;
};
;
;File: named.gem
14 matches
Mail list logo
