• Steps to reload zone files automatically?

    From Harshith Mulky@harshith.mulky@outlook.com to bind-users@lists.isc.org on Wed Jul 1 05:55:23 2020
    From Newsgroup: comp.protocols.dns.bind

    --_000_MAXPR01MB3950D30E4D0228BA8AD2BD8A816C0MAXPR01MB3950INDP_
    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable

    Hello

    Is there an automatic way we could use reloading the zone files rather than=
    using rndc reload or named restart?

    Any methods or links which can be shared to help us reload the zone files a= utomatically once we make changes to the zone files ( cron methods or shell=
    scripts)

    We are running bind with version as below

    # rpm -qi bind
    Name : bind
    Version : 9.9.5P1
    Release : 2.2.2
    Architecture: x86_64
    Install Date: Tue Oct 17 16:46:22 2017
    Group : Productivity/Networking/DNS/Servers
    Size : 747523
    License : ISC
    Signature : RSA/SHA256, Tue Oct 7 04:18:01 2014, Key ID b88b2fd43dbdc284 Source RPM : bind-9.9.5P1-2.2.2.src.rpm
    Build Date : Tue Oct 7 04:17:04 2014
    Build Host : cloud124
    Relocations : (not relocatable)
    Packager : http://bugs.opensuse.org
    Vendor : openSUSE
    URL : http://isc.org/sw/bind/
    Summary : Domain Name System (DNS) Server (named)
    Description :
    Berkeley Internet Name Domain (BIND) is an implementation of the Domain
    Name System (DNS) protocols and provides an openly redistributable
    reference implementation of the major components of the Domain Name
    System. This package includes the components to operate a DNS server. Distribution: openSUSE 13.2
    sataradnsVM1:~ #


    --_000_MAXPR01MB3950D30E4D0228BA8AD2BD8A816C0MAXPR01MB3950INDP_
    Content-Type: text/html; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable

    <html>
    <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=

    <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style>
    </head>
    <body dir=3D"ltr">
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">
    Hello</div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">

    </div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">
    Is there an automatic way we could use reloading the zone files rather than=
    using rndc reload or named restart?</div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">

    </div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">
    Any methods or links which can be shared to help us reload the zone files a= utomatically once we make changes to the zone files ( cron methods or shell=
    scripts)</div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">

    </div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">
    We are running bind with version as below</div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">

    </div>
    <div style=3D"font-family: Calibri, Helvetica, sans-serif; font-size: 12pt;=
    color: rgb(0, 0, 0);">
    <span># rpm -qi bind<br>
    </span>
    <div>Name &nbsp; &nbsp; &nbsp; &nbsp;: bind<br>
    </div>
    <div>Version &nbsp; &nbsp; : 9.9.5P1<br>
    </div>
    <div>Release &nbsp; &nbsp; : 2.2.2<br>
    </div>
    <div>Architecture: x86_64<br>
    </div>
    <div>Install Date: Tue Oct 17 16:46:22 2017<br>
    </div>
    <div>Group &nbsp; &nbsp; &nbsp; : Productivity/Networking/DNS/Servers<br> </div>
    <div>Size &nbsp; &nbsp; &nbsp; &nbsp;: 747523<br>
    </div>
    <div>License &nbsp; &nbsp; : ISC<br>
    </div>
    <div>Signature &nbsp; : RSA/SHA256, Tue Oct &nbsp;7 04:18:01 2014, Key ID b= 88b2fd43dbdc284<br>
    </div>
    <div>Source RPM &nbsp;: bind-9.9.5P1-2.2.2.src.rpm<br>
    </div>
    <div>Build Date &nbsp;: Tue Oct &nbsp;7 04:17:04 2014<br>
    </div>
    <div>Build Host &nbsp;: cloud124<br>
    </div>
    <div>Relocations : (not relocatable)<br>
    </div>
    <div>Packager &nbsp; &nbsp;: http://bugs.opensuse.org<br>
    </div>
    <div>Vendor &nbsp; &nbsp; &nbsp;: openSUSE<br>
    </div>
    <div>URL &nbsp; &nbsp; &nbsp; &nbsp; : http://isc.org/sw/bind/<br>
    </div>
    <div>Summary &nbsp; &nbsp; : Domain Name System (DNS) Server (named)<br>
    </div>
    <div>Description :<br>
    </div>
    <div>Berkeley Internet Name Domain (BIND) is an implementation of the Domai= n<br>
    </div>
    <div>Name System (DNS) protocols and provides an openly redistributable<br> </div>
    <div>reference implementation of the major components of the Domain Name<br=

    </div>
    <div>System. &nbsp;This package includes the components to operate a DNS se= rver.<br>
    </div>
    <div>Distribution: openSUSE 13.2<br>
    </div>
    <div>sataradnsVM1:~ #<br>
    </div>
    <span></span><br>
    </div>
    </body>
    </html>

    --_000_MAXPR01MB3950D30E4D0228BA8AD2BD8A816C0MAXPR01MB3950INDP_--
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Erich Eckner@bind@eckner.net to Harshith Mulky on Wed Jul 1 09:21:16 2020
    From Newsgroup: comp.protocols.dns.bind

    This message is in MIME format. The first part should be readable text,
    while the remaining parts are likely unreadable without MIME-aware tools.

    ---1945468810-1298638614-1593588081=:807583
    Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    On Wed, 1 Jul 2020, Harshith Mulky wrote:

    Hello

    Hi,

    Is there an automatic way we could use reloading the zone files rather than using rndc reload or named restart?

    Shouldn't the design be, that: Whoever changes the zone file, runs "rndc reload" afterwards?


    Any methods or links which can be shared to help us reload the zone files automatically once we make changes to the zone files ( cron methods or shell scripts)

    If you really want to go that path (see suggestion above), have a look at inotifywait from inotifytools (I'm not sure, how the package is called in suse):

    https://linux.die.net/man/1/inotifywait


    We are running bind with version as below

    # rpm -qi bind
    Name        : bind
    Version     : 9.9.5P1
    Release     : 2.2.2
    Architecture: x86_64
    Install Date: Tue Oct 17 16:46:22 2017
    Group       : Productivity/Networking/DNS/Servers
    Size        : 747523
    License     : ISC
    Signature   : RSA/SHA256, Tue Oct  7 04:18:01 2014, Key ID b88b2fd43dbdc284 Source RPM  : bind-9.9.5P1-2.2.2.src.rpm
    Build Date  : Tue Oct  7 04:17:04 2014
    Build Host  : cloud124
    Relocations : (not relocatable)
    Packager    : http://bugs.opensuse.org
    Vendor      : openSUSE
    URL         : http://isc.org/sw/bind/
    Summary     : Domain Name System (DNS) Server (named)
    Description :
    Berkeley Internet Name Domain (BIND) is an implementation of the Domain
    Name System (DNS) protocols and provides an openly redistributable
    reference implementation of the major components of the Domain Name
    System.  This package includes the components to operate a DNS server. Distribution: openSUSE 13.2
    sataradnsVM1:~ #




    regards,
    Erich

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl78OW8ACgkQCu7JB1Xa e1poQRAAuGVb4Nr+qv82wtzIGkgXElOY8fW+kWf0p8UbZAiQZvVK25RlSytbmO2e A5Ie7ttJbMDM3qwSJfN69eDj3h8ctL6pVtsazIMUJpT8jGKvncHbm5xLyJUgCWt0 /GaO9gvwthbkmkfA5TyWPAk8SdeHDFS03RsbHcONs2MWwmUYWBeooX3N48DwX6r+ DlNJVIyAi3H2ApT2V/BZ+XTqE5wW9IPZbUqB9wwzzIib+pRq3EOoBpLnXMMZsI96 IJu/7mpTaV8XtY6K8Q+LeAdg86PrXlwg3sgd4ss0b9VkwvH3dELqMPn4I6DwfFkM 4H1AZU413udKx0R4a9CEZfBPHOo0IHAEZsAV3A0gi8/HUU4pUZVhHXza0I5imgHc rXyl/g6dXhPx/pYIWZmLACYkyNQoJNZEvek9dLn9+ywy2C/jr4H7ivIC1q3I2og5 IaKNHSv6l9VqHK03fCjpm+xxSY5U758N1oReS7khJnBWPGNUh5jLYnC/NXUgEz5a 4hx7K/Syg+WXfAH3TZPx+RCbARNcP7dz3sbpRWu7J6eL4Zhxmht2RcsMtSB2Ckpv dgZ4/5zD3e0Fi0xDyvnfEoNMp8ihBYUrsvL7vUJXv7ek/VMG6QHJSKxk0U94/io6 xQZXizzvgeHWnYsaWhnR/NkVyyk23R3v+czHf+In5/iOeNU/S/c=
    =uZm6
    -----END PGP SIGNATURE-----
    ---1945468810-1298638614-1593588081=:807583--
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From G.W. Haywood@bind@jubileegroup.co.uk to bind-users on Wed Jul 1 16:06:21 2020
    From Newsgroup: comp.protocols.dns.bind

    This message is in MIME format. The first part should be readable text,
    while the remaining parts are likely unreadable without MIME-aware tools.

    ---1463810772-946371772-1593615982=:13515
    Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT

    Hi there,

    On Wed, 1 Jul 2020, Harshith Mulky wrote:

    Is there an automatic way we could use reloading the zone files
    rather than using rndc reload or named restart?

    It should be trivial to implement this, but I'm not sure that I'd want
    to do it on a server of mine.

    We are running bind with version as below

    # rpm -qi bind
    Name : bind
    Version : 9.9.5P1
    ...

    https://kb.isc.org/docs/bind-9-end-of-life-dates

    Date: Wed, 08 Jun 2016 20:09:54 +1000
    From: Mark Andrews <marka@isc.org>
    To: Harshith Mulky <harshith.mulky@outlook.com>
    ...
    ... Harshith Mulky writes:
    I have bind Running on following Version:

    bind-9.8.2-0.17.rc1.el6.x86_64

    Upgrade.

    Plus ça change, plus c'est la même chose...

    --

    73,
    Ged.
    ---1463810772-946371772-1593615982=:13515--
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Chuck Aurora@ca@nodns4.us to bind-users on Wed Jul 1 16:21:20 2020
    From Newsgroup: comp.protocols.dns.bind

    On 2020-07-01 00:55, Harshith Mulky wrote:
    Is there an automatic way we could use reloading the zone files
    rather than using rndc reload or named restart?

    Within named, no. Furthermore a restart of named for changed zone
    data was never a good idea. Likewise, "rndc reload" only makes sense
    when numerous zones were changed at one time; otherwise you would use
    "rndc reload zone-name [view-name]".

    Any methods or links which can be shared to help us reload the zone
    files automatically once we make changes to the zone files ( cron
    methods or shell scripts)

    A different paradigm which would do this better would be to use
    dynamic zones (RFC 2136.) To do this you would set an update-policy
    for the zone[s] (or globally) and submit updates using nsupdate(8)
    or other RFC 2136 client.

    Ideally you would ONLY use dynamic updates to change zone data, but
    there's also freeze and thaw functions in rndc(8) for those who want
    to edit a zone file for Old Time's Sake. (The freeze will lose your
    zone updates history.)

    Dynamic DNS is covered well in the BIND 9 ARM. There are probably
    also some articles at the ISC KB.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Tony Finch@dot@dotat.at to bind-users on Thu Jul 2 22:04:49 2020
    From Newsgroup: comp.protocols.dns.bind

    Chuck Aurora <ca@nodns4.us> wrote:

    nice domain name :-)

    On 2020-07-01 00:55, Harshith Mulky wrote:

    Any methods or links which can be shared to help us reload the zone
    files automatically once we make changes to the zone files ( cron
    methods or shell scripts)

    A different paradigm which would do this better would be to use
    dynamic zones (RFC 2136.) To do this you would set an update-policy
    for the zone[s] (or globally) and submit updates using nsupdate(8)
    or other RFC 2136 client.

    Yes, this is the way I like to do things. Specifically, it's fairly easy
    if you configure your zones with `update-policy local`, and you use
    `nsupdate -l` to modify the zone. That way you get a fairly secure setup
    with very little configuration effort.

    You're all probably bored of me plugging nsdiff, but I wrote it to make
    it easier to update zones this way - http://dotat.at/prog/nsdiff/
    (My production zones are updated by a cron job that feeds database dumps
    into nspatch, and I edit my test and personal zones using nsvi, both of
    which are wrappers around nsdiff and nsupdate.)

    Ideally you would ONLY use dynamic updates to change zone data, but
    there's also freeze and thaw functions in rndc(8) for those who want
    to edit a zone file for Old Time's Sake. (The freeze will lose your
    zone updates history.)

    You can preserve the history if you configure the zone with `ixfr-from-differences`.

    Tony.
    --
    f.anthony.n.finch <dot@dotat.at> http://dotat.at/
    democracy, participation, and the co-operative principle
    --- Synchronet 3.18a-Linux NewsLink 1.113