Mailinglist Archive: opensuse (389 mails)

< Previous Next >
Re: [opensuse] Why are nsupdate changes not persistent?
  • From: Per Jessen <per@xxxxxxxxxxxx>
  • Date: Sat, 16 Mar 2019 09:07:44 +0100
  • Message-id: <q6iasg$fuq$1@saturn.local.net>
Marc Chamberlin wrote:

dig does show that indeed the TXT record was added and I see that the
jnl file - example.com.jnl has been created. However neither of the
config files for example.com in /etc/named.d/local/master/example.com
or /var/lib/named/etc/named.d/local/master/example.com has been
updated yet, as expected...

Ah. No, those configs should not be updated. The zone files
in /var/lib/named/ are what matters:

nameserver:/var/lib/named/master # l example*
-rw-r--r-- 1 named named 11891 2019-03-15 18:05 example.com
-rw-r--r-- 1 named named 732 2019-03-16 08:52 example.com.jnl

(I've just now added a txt record, hence the 0852 timestamp on the
journal).

However, it still is not persisted into
/etc/named.d/local/master/example.com.  The jnl file is still in the
chrooted directory...

Aha, now I see what is happening.

You have put your zone file in

file "/etc/named.d/external/master/example.com";

That won't work, at least not with the current init-scripts supplied by
openSUSE.

I suggest you use "/var/lib/named/master/example.com" instead.

config and data are kept separately - in /etc/named.{d/,conf} and
in /var/lib/named/, respectively. The config is copied into the chroot
dir, but the data is kept/maintained in /var/lib/named/. In your
zonefile config, just use something like this:

zone "example.com" {
type master;
------> file "master/example.com";
forwarders { };
notify yes;
etc etc



--
Per Jessen, Zürich (12.1°C)
member, openSUSE Heroes


--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups