SCSIraidGURU’s World

nslookup pointed to instead of the proper IP of both DNS servers.   Some think it is a bug in 18.04.

nslookup pridns



$ sudo rm -f /etc/resolv.conf
$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
$ ls -l /etc/resolv.conf

lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

$ sudo reboot

I just completed installing my Primary and Second DNS servers.  Currently, I use the Fortinet 60E firewall for DNS.  I want to move these lookup off the firewall.  The two servers I setup have ACL lists for good computer subnets on them.  I used Fortinet’s DNS servers as the forwards.  Google DNS can be hacked and redirected.  You are better off using your ISP DNS servers. 

Sudo systemctl -l status bind9 gets check hint errors

Use wget command to retrieve file and store to /etc/bind/db.root (Debian / Ubuntu Linux), enter:
# wget --user=ftp --password=ftp -O /etc/bind/db.root

Under Red Hat / CentOS / Fedora Linux, default location is /var/named/named.root, enter:
# wget --user=ftp --password=ftp -O /var/named/named.root

Reload rndc to update information, enter:
# rndc reload

I added a second subnet to the DNS and DHCP servers.  My goal is move DHCP off of the 60E.   Now all my audio/video hardware is on its own subnet.   The next goal is a slave DHCP server on the slave DNS server.

Close Menu