It's not entirely clear to me what is happening. I imagine that bind
is not running, due to errors in your configurations, so it is unreachable. If this isn't helpful, please edit your post to include the command you're running, and additional output.
When you interact with bind
, are you using systemctl
? For example:
systemctl restart bind9
When you do this, does the command spit out any errors? Normally when something is wrong, it will direct you to look at journalctl
. What is the system telling you is wrong?
You can check if bind is running using systemctl status bind9
, or ps aux | grep named
, and possibly rndc status
.
Maybe you have your /etc/bind/named.conf.local
correct, but you did not post one, so be sure that you have the zone entries in that file. You will need one per domain, and one per subnet served:
zone "example.tld" {
type master;
file "/etc/bind/zones/example.tld.zone";
};
zone "1.168.192.in-addr.arpa" {
type master;
file "/etc/bind/zones/192.168.1.zone";
};
Here is a working /etc/bind/named.conf.options
, however, I've adjusted the IP to read .200
, since .888
is not a valid IP.
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 0.0.0.0;
// };
//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https://www.isc.org/bind-keys
//========================================================================
recursion yes;
allow-recursion {localnets; 192.168.1.0/16;};
forwarders {
192.168.1.1;
};
dnssec-enable yes;
dnssec-validation auto;
dnssec-lookaside auto;
auth-nxdomain no; # conform to RFC1035
listen-on { 192.168.1.200; 127.0.0.1; };
// listen-on-ipv6 { any; };
};
After you've double-checked the settings, restart bind
and find the logs and output to determine the problem. Please post the exact commands, and logs you've found, as there may be even more wrong and it will be hard for anybody to help without all of the details.
An additional tip would be to change one thing at a time. Change your IP, verify you still have connectivity. Then, adjust bind, etc. Take an iterative approach, and ensure that each time you make a change, you haven't broken everything else.