Hi,
You can use the "serial-update-method" key-word to define how BIND will update
the serial number in a dynamic zone's SOA record.
It may be defined within "options", views, and zones.
Legal values are "date", "increment", and "unixtime".
The default setting is "serial-update-method increm
Hi,
I have configured Dynamic DNS in bind and I see the date in the serial
number is not getting updated in the recommended format MMDDnn.
Yesterday I created the DDNS zone and the serial number was 2024092501 but
today when the zone is updated, it just increments to 2024092502 and not
202409
Our 'special' zone definitions are less than 10kb (at the moment), so
the 64kb limit isn't an issue. And if it ever is, it can be broken up
into several 'included' .conf files.
The 255-character string limit isn't a problem with base64:
base64 -w 250 special.conf | sed 's/^/"/;s/$/"/' | tr -d
Are you leveraging your existing configuration management tools (e.g.
Puppet, Ansible, Chef)?
Ansible (my choice of poison) works well for this type of situation I find,
particularly because a lot of work can be done via Jinja templating. This
trivial example hopefully illustrates what I mean:
4 matches
Mail list logo
