7 Čec
2023
7 Čec
'23
12:31
Yes, it is likely that the missing unique-id's are the only problem. I
was able to reproduce the issue with that setup - I'm quite surprised
that such a faulty catalog zone actually worked with 3.0.5.
So, Daniel, try adding the unique-id's first.
Regards,
David
On 2023-07-07 12:20, Tuomo Soini wrote:
On Thu, 6 Jul 2023 20:51:04 +0200
Daniel Gröber <dxld(a)darkboxed.org> wrote:
but the zones pointed to don't get
instantiated (as seen by `knotc
zone-status`). Any ideas what could have changed to break this?
Your catalog zone doesn't follow proper catalog format. you should have
uniqueid per zone. so format is:
<uniqueid>.zones.<catalog-zone>. 0 PTR domain.tld.
you can select any method to generate uniqueid. We originally decided
to use uuid but after initial testing we moved to md5sum of
"domain.tld.primary.server.dns-name." so we can re-generate always same
uniqueid. Problem with uuid was we'd need to have separate database to
store uuid domain.tld. combinations. you could use any "salt" instead
of primary.server.dns-name. but for our purposes server dns name was
unique.
Some kind of hash of domain is not enough in case you need to handle
moving domain from one system to another where catalog interpreter can
be secondary server for multiple different primary servers.