I have two VM's running OpenSUSE 15, one master and one slave.
Master is running well and transfer the zones file to the slave correctly but if I stop the bind on master server, slave should respond to clients but he doesn't. I configured two clients with only the slave server as DNS, not working.
What am I doing wrong ?
By the way, it is a test environment for my school project
Master conf file:
# Config dnslinux.lab
zone "dnslinux.lab" {
type master;
file "/var/lib/named/dnslinux.db";
allow-transfer { 192.168.88.131; };
#allow-update { 192.168.88.131 ; };
notify yes;
also-notify { 192.168.88.131; };
};
# Config zone inverse
zone "88.168.192.in-addr.arpa" {
type master;
file "/var/lib/named/reverse.dnslinux.db";
allow-transfer { 192.168.88.131; };
#allow-update { 192.168.88.131 ; };
notify yes;
also-notify { 192.168.88.131; };
};
SLAVE CONF FILE(can't share it other way)
Zones files
main file
$TTL 10800
@ IN SOA ns1.dnslinux.lab. root.dnslinux.lab. (
2020012301 ; Serial
30 ; Refresh
10 ; Retry
1w ; Expire
1h ) ; Negative Cache TTL
@ IN NS ns1.dnslinux.lab.
@ IN NS ns2.dnslinux.lab.
; DNS Servers
ns1 IN A 192.168.88.130
ns2 IN A 192.168.88.131
; Machines
docker IN A 192.168.88.128
Reverse zone
$TTL 10800
@ IN SOA ns1.dnslinux.lab. root.dnslinux.lab. (
2020012301 ;
30 ;
10 ;
1w ;
1h ) ;
@ IN NS ns1.dnslinux.lab.
@ IN NS ns2.dnslinux.lab.
; DNS Servers
130 IN PTR ns1.dnslinux.lab.
131 IN PTR ns2.dnslinux.lab.
; Machines
128 IN PTR docker.dnslinux.lab.
This is the first time I posted here, please let me know if I'm not clear.
Best Answer
Result of dig command when i run it on my Docker VM
I also test a ping to ensure i can reach the slave.
Dig does work when i run it on the slave server himself. dig result . I configured slave's resolv.conf file as follow:
Here are the logs i get when i restart named on slave:
EDIT: I solved the problem, it was the firewall blocking port 53 on public zone network (i don't know why my VMs network has been set to public), I went into yast > Security and Users > Firewall > Then i add DNS protocol on public. I noticed my mistake with
dig @ip_slave_server client.name
and by installing nmapnmap -v -p 53 192.168.X.X
.