That's really strange because the file resolv.conf is not found on the system. Edit: I miss-spoke on that, I did find it.
Also from the wiki..
Also create a new resolve.conf file:
sudo touch /etc/resolv.conf.new
Why would we use resolv
.conf.new instead of resolve
You will be creating or editing the following config files in these new directories
At least here it's consistent.
Change all the file permissions per instructions in named.conf:
// /etc/bind/named.conf root:root 644
// /etc/bind/rndc.key root:bind 640
// /etc/bind/rndc.conf root:root 600
// /etc/resolv.conf root:root 644
// /etc/bind root:bind 775, chmod g+s => drwxrwsr-x
// /etc/dhcp3 root:root 755
// /etc/dhcp3/dhcpd.conf root:root 644
The same here still consistent.
Then here is where it all changes.
When and if you are feeling lucky, rename the original directories and then rename the new directories to take their place:
sudo mv /etc/bind /etc/bind.original
sudo mv /etc/bind.new /etc/bind
sudo mv /etc/dhcp3 /etc/dhcp3.original
sudo mv /etc/dhcp3.new /etc/dhcp3
sudo mv /etc/resolve.conf /etc/resolve.conf.original
sudo mv /etc/resolve.conf.new /etc/resolve.conf
In that last bit of code at the bottom you have resolve
.conf.new when you were using resolv
But earlier we didn't name it resolve
.conf.new we named it resolv
I would be glad to change it but....
Posted by: tux-box1
Uh, I was not aware that I had permission to do that!
This action has been automatically identified as harmful, and therefore disallowed. If you believe your edit was constructive, please contact an administrator, and inform them of what you were trying to do. A brief description of the abuse rule which your action matched is: Link spamming 2