named - writeable file 'master/2001.db8.1234.1': already in use: /etc/named.d/enidan-reverse.conf:40
I run a named with multiple views (four) - in such a setup, you cannot have independent / out-of-view zones so each view includes common zones, such as 'enidan-reverse' (just reverse zones). For the reverse ipv6 zone, we want to do dynamic updates - hence we have 'allow-update { localhost; };' for that zone. Previously, named or named-checkconf did not complain, but I am attempting an upgrade to 15.2 and the new named-checkconf complains. Plenty of hits with google, but no solutions other than disabling the checkconf. Some people suggest adding 'DISABLE_ZONE_CHECKING=yes' to /etc/sysconfig/named, but that variable is not supported in our named setup. For now, I need the named update more than the dynamic ipv6 updates, so I'll probably just disable it, but surely there is a way out of this? -- Per Jessen, Zürich (16.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
On Mon, May 24, 2021 at 2:34 PM Per Jessen <per@computer.org> wrote:
I run a named with multiple views (four) - in such a setup, you cannot have independent / out-of-view zones so each view includes common zones, such as 'enidan-reverse' (just reverse zones).
For the reverse ipv6 zone, we want to do dynamic updates - hence we have 'allow-update { localhost; };' for that zone.
Previously, named or named-checkconf did not complain, but I am attempting an upgrade to 15.2 and the new named-checkconf complains.
Plenty of hits with google, but no solutions other than disabling the checkconf. Some people suggest adding 'DISABLE_ZONE_CHECKING=yes' to /etc/sysconfig/named, but that variable is not supported in our named setup.
For now, I need the named update more than the dynamic ipv6 updates, so I'll probably just disable it, but surely there is a way out of this?
This sounds like example 4 in https://kb.isc.org/docs/aa-00851
Andrei Borzenkov wrote:
On Mon, May 24, 2021 at 2:34 PM Per Jessen <per@computer.org> wrote:
I run a named with multiple views (four) - in such a setup, you cannot have independent / out-of-view zones so each view includes common zones, such as 'enidan-reverse' (just reverse zones).
For the reverse ipv6 zone, we want to do dynamic updates - hence we have 'allow-update { localhost; };' for that zone.
Previously, named or named-checkconf did not complain, but I am attempting an upgrade to 15.2 and the new named-checkconf complains.
Plenty of hits with google, but no solutions other than disabling the checkconf. Some people suggest adding 'DISABLE_ZONE_CHECKING=yes' to /etc/sysconfig/named, but that variable is not supported in our named setup.
For now, I need the named update more than the dynamic ipv6 updates, so I'll probably just disable it, but surely there is a way out of this?
This sounds like example 4 in https://kb.isc.org/docs/aa-00851
Yes, it does sound a lot like that - "How do I share a dynamic zone between multiple views?". Hmm, will have to go and study, thanks for the link. -- Per Jessen, Zürich (14.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
participants (2)
-
Andrei Borzenkov -
Per Jessen