TODO - tell about the DNSSEC time sink and how to avoid it.
More VMS will be added later, throughout the lab.
The instructions go through this step-by-step - However, there are some clarifications:
Add the appropriate variant of the following to /etc/named.conf
zone "theirco.abc1234.com" {
type slave;
file "slaves/theirco.abc1234.com";
masters{
10.150.72.2;
};
};
The instructions imply that something needs to be added to the options
section. This is false.
My option section contains only
directory "/var/named";
and not even that is needed.
The instructions here are incomplete and inefficient. Perform these steps:
systemctl stop named
rm -rf /var/named/slaves/
systemctl start named
Convert the binary file to text with the following command, replacing abc1234 where needed:
named-compilezone -f raw -F text -o /var/named/slaves/theirco.abc1234.com.dns theirco.abc1234.com /var/named/slaves/theirco.abc1234.com
Finally, cat /var/named/slaves/theirco.abc1234.com.dns
Here we’re creating another CentOS-BIND-DNS stack to serve a subdomain.
The instructions have been using subnets
On bench machine 1 (the 71 network for me), Full-clone the base CentOS_7.3 VM.
The instructions will call it CentOS2.
I will call it LOOOP.
Use the GUI to set the ip information. I placed LOOOP on 71.100
yum clean all
yum --disablerepo=\* --enablerepo=base,extras,updates update
hostnamectl set-hostname [name]
vim /etc/selinux/config
SELINUX=permissive
shutdown -r now
Verify changes with sestatus
yum -y install bind bind-utils
firewall-cmd --zone=public --permanent --add-service=dns
vim /etc/named.conf
options{
directory "/var/named";
};
zone "mgmt.myco.abc1234.com" IN{
type master;
file "mgmt.myco.abc1234.com.dns";
};
# Reverse zone here.
The mgmt
domain needs two fake entries. Almost everything needed can be copy/pasted from CentOS1, or LambSauce in my case.
I don’t have subnets, so whichever server is set as DNS for a host will be the one they ask for reverse lookup.
named-checkconf
named-checkzone
If both check commands are fine, and it starts, and systemctl status named -l
looks okay, then it’s probably okay.
This section has two parts
While the report does ask for a DNS topology, nothing needs to be done In Lab to create this, as long as you have notes somewhere of what VMs do what job.
Report question 3.1 asks about these network traces. You need two:
This is where I got in my second lab section.
My first lab session was less productive than expected, due to a number of things I had to fix from lab5 and errors in the lab6 instructions. I hope those following my notes fare better.
Session | Time Spent | Progress |
---|---|---|
In Lab, Nov 19th | 2 Hours | Activity 1, signoff 1. |
Lab Nov26th | 2 hours | Through 2.2, no signoff |