Hot answers tagged bind
In the DNS context, a TTL defines the duration that a resource record (RR) may be cached by any resolver. NS RRs are part of what is sometimes called the zone's infrastructure records. Infrastructure RRs (which include SOA, NS and MX RRs) are unique in that they return other names not addresses, as such they should be stable and to minimize DNS access can ...
The forwarders that you have configured will only cause problems when running a validating resolver as the Opendns servers do not cooperate when doing DNSSEC validation. I suppose it might mostly work anyway for you as you didn't specify forward only, so named will fall back to resolving things on its own more or less all the time as the forwarders keep ...
You then may try to manually activate it: http://manpages.ubuntu.com/manpages/xenial/man8/update-rc.d.8.html (legacy) Example: # update-rc.d bind9 enable On systemd, it would be: # systemctl enable bind9
Samba has the capability to automatically update the BIND zone files via Kerberos. You have to configure bind with auto update. Check this article for full configuration and integration between Bind and Samba as domain controller Samba/Active Directory domain controller
It works as you expect, you can mask your public domain if you add the zone to your internal DNS resolver. If you're using your ISP's DNS resolvers, you will have to set up your own as mentioned in your question. Your internal DNS resolver must be added to the resolv.conf file (or equivalent on Windows) on every machine on your network, and must allow ...
Just adding onto roothahn's answer as I feel it could use a little explanation, what you will want to do is systemctl enable bind9. Ubuntu 16.04 uses systemd instead of init, so most services are done via systemctl, rather than service and /etc/init.d scripts (which I assume still exist for compatibility reasons). In terms of starting, restarting and ...
Only top voted, non community-wiki answers of a minimum length are eligible