I have set up a bind9 name server and created a dedicated (internal) subdomain, which can be updated by everybody for whatever purpose. There is only one server, running a [email protected]:/tmp# rndc freeze [email protected]:/tmp# rndc thaw A zone reload and thaw was started. Obviously there is some kind of delay in my setup and I need to know why and how to get rid of it.
The setup is very in simple and does work in general, but there is a delay of up to several minutes, before updates have effects i.e. I don't know the answer but I'm pretty sure this is somehow related to the fact that the problematic record is a glue record.
In the hopes of saving someone else time (and mine in the future should I forget in the future).
In truth getting this setup is relatively simple - you just have to know the right set of steps in order to get it done right.
With bind9 it is easily possible to setup your own dynamic DNS service.
This set of scripts use the 'nsupdate' tool and authenticated communication, to update the DNS entries.
It is quite often coupled with dhcp to provide dynamic network services that have hostnames follow the appropriate machines around. To do it securely, you need to first create a secret key. For every zone you want to allow dynamic updates (for this specific key), you need to add an That's all we have to do.
Many of the free services limited their service offer over the time, or the service depends on buying a product (like a DSL router).First, you need to move all of your zone files to /var/lib/bind or another folder which you want to keep your zone files in.It really doesn't matter they're move to, just so long as they are not in /etc/bind. 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1#5353 Non-authoritative answer: in nameserver = ( 2015033109 ; serial 604800 ; refresh (1 week) 86400 ; retry (1 day) 2419200 ; expire (4 weeks) 604800 ; minimum (1 week) ) NS in. mail A 10.30.1.4 $TTL 600 ; 10 minutes test A 220.127.116.11 abc NS # [email protected]:/tmp# nslookup -port=5353 -type=NS in.