NAMEd Your Poison
This write up will be a lot less talk and a lot more action. There are a lot of tutorials out there but if you need some better in-depth info, I highly recommend the BIND documentation that ISC has put together. They really have done a fantastic job.
Little note before we get rolling. This setup will allow for being a caching server or all the way to being authoritative (be your own name server). The config files below will have all the meat required to be authoritative, but will be commented out. The initial setup will just be caching. This will give you time to get the system all setup and start using the system, then you can go back through and uncomment the parts you want to use.
I have used this setup for many many years and it has treated me well.
Here comes a warning...
As you copy and paste these configs into your system, please be sure to check it over real good and change names and IP's to fit your setup. It may require some digging around if you miss something. Just a heads up!
And here we go!
- setup will be jailed into /opt/named
- folder and file structure:
/opt/named/ ├── dev/ │ ├── null │ └── random ├── etc/ │ ├── localtime │ ├── namedb/ │ │ ├── external/ │ │ │ ├── db.11.22.33 │ │ │ ├── db.example.net │ │ │ └── named.conf │ │ ├── include/ │ │ │ ├── include.mx │ │ │ ├── include.ns │ │ │ └── include.soa │ │ ├── internal/ │ │ │ ├── db.10.0.0 │ │ │ ├── db.127.0.0 │ │ │ ├── db.localhost │ │ │ ├── db.roots │ │ │ └── named.conf │ │ ├── log/ │ │ │ ├── log │ │ │ └── named.run │ │ └── secondary/ │ │ └── named.conf │ ├── named.conf │ └── policy/ │ ├── bind.config -> bind.txt │ └── bind.txt ├── key/ │ ├── internal.mkeys │ ├── internal.mkeys.jnl │ └── session.key └── var/ | ├── data/ | └── run/ | | └──/etc | ├── named.conf -> /opt/named/etc/named.conf | └── rndc.key | └──/usr/lib/systemd/system/named.service
- folder and file structure: