Bind dynamic updating zone records
Updated version This is an updated guide for Ubuntu 12.04.
If you use an older version of Ubuntu, then you might want to check out the old guide, that was written for Ubuntu 8.04.
before you proceed with the installation and configuration of bind nameserver make sure that bind DNS server is exactly what you want.
Sample scenario notes to help you ready this DNS bind howto:dnsutils is not compulsory package to run bind webserver, but we will use a dig command which is part of this package as a testing tool of your bind configuration. This IP address is used in case that a local DNS server do not know the answer the a name resolution query.
At this stage we will need to create a new zone file for a domain In IP address of a DNS server in many cases is provided by your Internet provider.
If you look in Microsoft DNS, you will see that the record is created.
Upon close inspection of the security (Advanced view), you will see that the Linux host itself (as seen by its Kerberos principle name / computer object name), registered the record. NON-SECURE DYNAMIC UPDATE ZONES As discussed earlier, what happens if the DNS zones are configured for "None" or "Nonsecure and Secure"? In both scenarios, where we set the DNS zone to either None" or "Nonsecure and Secure", we will see a correctly formatted fully qualified name but then see a failure. DNS will delete the DNS record and discard the authentication token. This means until the NEXT cycle runs in 15 minutes, the client will be unresolvable (and cause great confusion every 15 minutes).
Default setup and execution of bind on Debian or Ubuntu may take around 200MB of RAM with no zones added to the config file.