How to Install and Configure Bind 9 (DNS Server) on Ubuntu / Debian System

5 Responses

  1. FH says:

    Nice walktrough of a complex issue.

    You might reconsider using .local as your intranet name.

    Best practice is to use a FQDN and prefix it with eg. lan being lan.domain.tld. The need for it will show when you have to build a Microsoft AD.

    In the long run avoiding using .local will result in a more structured network and it will become more obvious if you operate mixed network using both Microsoft Windows, macOS and LInux.

    Also .local is a zeroconf domain used exclusively in zeroconf networking.

  2. Brad says:

    First off, I’m a complete Linux newbie!

    The restart command that you have above did not work for me. I had to run sudo /etc/init.d/bind9 restart to restart bind. Does this make any difference? How can I ensure that Bind is running as a service?

    Thanks.

  3. Taufik says:

    Thanx for sharing nice tutorial

  4. Robert de Wild says:

    Hello. Great write up thanks. I was able to follow and configure your directions pretty much to the tee. But, when I get to the NSLOOKUP it always just resolves to 127.0.0.53
    No idea really where that is coming from. I do have a /etc/resolv.conf that lists that address as nameserver.
    However, if I change that file, it just gets overwritten again on the next reboot.
    Any ideas?

  5. jackson bakari says:

    hi
    i just install my new bind9 dns but when i check to the ‘http://dnscheck.pingdom.com/’ i got this massage

    You don’t have permission to access / on this server.
    what does it means

Leave a Reply

Your email address will not be published. Required fields are marked *