If your IP address changes daily, you may want to reduce this to 5min to have a smaller timeframe during which your server is not available.
However, please note that there are some scenarios that will require administrator’s attention and some testing of exact requirements before deploying Knot DNS to a production environment.These cases include deployment for a large number of zones (DNS hosting), large number of records in one or more zones (TLD), or large number of requests.To run the script regularly, simply set up a cronjob.You can do so by running This sets the update interval to 15min.For example if my computer is named mycomputer, it will try to upload the dyn.zone with
That option is absolutely needed if you have several domains in the “option domain-name” field (the “search” domains that will be in /etc/resolv.conf), or it could try to add the hostname mycomputer.static.to the dyn.zone.
For IPv6, the script can alternatively attempt to detect the correct local address to use.
The sample file contains comments that should explain everything.
Alternatively, some routers can be configured to do this themselves. Please read this guide carefully and make sure you understand the security implications of what you are doing. If it were run-time configurable, then a user could call the script with her own configuration file, gaining access to all domains BIND lets you configure. They are using Python 2, so make sure you have that installed.
If you want to put the files in another directory, change the configuration file name accordingly. There are two scripts: One is used for clients to detect their current external IP address, and one is used to do the actual update of the domain.
Knot DNS is a high-performance open-source DNS server.