Okay, so the direct transition 2.6.5 -> 3.0.5 might
be easier.
Definitely, you don't have to start from scratch. If you don't use
`journal-content: all`, I would drop the whole journal.
Other databases (KASP) should be compatible enough.
Well that's a relief.
So it's enough to
# knotc zone-flush
followed by a
# knotc zone-freeze
followed by a
# knotc stop
Then recursively tar up the knot working directory and unpack
it all into the knot working directory on the new servers and
fire knot up? Could it really be that smooth? Discounting all
the removed/changes in the config nomenclature, of course.
Thank you VERY much for the reply, Daniel.
--Chris
Daniel
On 4/9/21 8:42 AM, Chris wrote:
> On 2021-04-08 23:35, Daniel Salzman wrote:
>> Hi Chris,
>>
>> What is your OS and Knot DNS package source?
> Hi. Thank for the reply. Sorry for being on the wrong list.
> We're on FreeBSD. Migrating to ports/dns/knot3 (knot 3.0.4)
> from knot 2.6.5.
>
> Thanks again!
>
> --Chris
>>
>> Daniel
>>
>> On 4/9/21 8:30 AM, libor.peltan wrote:
>>> Hi Chris,
>>>
>>> first of all, you seem to be talking about Knot DNS, so it's proper to
>>> switch to correct mailing list, instead of Knot Resolver's one.
>>>
>>> I assume you have read all the single-version migration guides below
>>>
https://www.knot-dns.cz/docs/3.0/singlehtml/index.html#upgrade-2-6-x-to-2-7…
>>> . It's clear that when migrating over multiple
>>> versions, you need to take care about all the notes at once.
>>>
>>> What databases exactly are you talking about? Knot DNS uses multiple
>>> databases for different purposes, e.g. journal or KASP DB. The good news
>>> is, their format does not change much, and when it does,
>>> it's usually backwards-compatible, with some exceptions.
>>>
>>> I would strongly recommend that you clone your environment, perform the
>>> migration in some "playground" setup first, and observe if
everything
>>> went well; all before migration your production setup ;)
>>> Should you encounter any issues, please contact us on our mailing-list.
>>>
>>> Anyway, you might consider a multi-step migration, so that you would
>>> migrate by just one (major) version at once, like this: 2.6.5 -> 2.7.8
->
>>> 2.8.5 -> 2.9.9 -> 3.0.5.
>>>
>>> Thanks!
>>>
>>> Libor
>>>
>>> Dne 09. 04. 21 v 8:13 Daniel Salzman napsal(a):
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: [knot-resolver-users] Any "gothcas" going from 2.65 to
3.04 I
>>>> should know about?
>>>> Date: Thu, 08 Apr 2021 23:03:54 -0700
>>>> From: Chris <knot(a)tacomawireless.net>
>>>> Reply-To: Knot Resolver Users List
<knot-resolver-users(a)lists.nic.cz>
>>>> To: knot-resolver-users <knot-resolver-users(a)lists.nic.cz>
>>>>
>>>> Hi. Moving a couple of our servers to new hardware, and
>>>> taking that opportunity to upgrade some of the services
>>>> at the same time. The main one being knot. Moving from
>>>> a 2.65 context to 3.04. I've read the upgrade doc, and
>>>> while there isn't a 2.65 --> 3.04. It appears for our
>>>> environment that the changed/removed stanzas won't
>>>> have much of an impact *except* as they relate to the
>>>> database. That is; it appears that it isn't going to
>>>> be a smooth transition, as they appear to be incompatible.
>>>> Is that right? Do I need to rewrite all the keys &&
>>>> serials, and start from scratch? If so, as we have
>>>> a huge number of domains, this will be an enormous task.
>>>> Is this avoidable?
>>>>
>>>> Thank you for any and all insight into this transition.
>>>>
>>>> --Chris