On 21/04/2021 03:36, Jack Craig wrote:
netstat -nap | grep named
tcp 0 0 127.0.0.1:53 http://127.0.0.1:53 0.0.0.0:* LISTEN 1090819/named tcp 0 0 127.0.0.1:953 http://127.0.0.1:953 0.0.0.0:* LISTEN 1090819/named udp 0 0 127.0.0.1:53 http://127.0.0.1:53 0.0.0.0:* 1090819/named unix 2 [ ] DGRAM 3212045 1090819/named unix 2 [ ] STREAM CONNECTED 3212051 1090819/named
after
nap | grep named
tcp 0 0 127.0.0.1:53 http://127.0.0.1:53 0.0.0.0:* LISTEN 1258277/named tcp 0 0 127.0.0.1:953 http://127.0.0.1:953 0.0.0.0:* LISTEN 1258277/named udp 0 0 127.0.0.1:53 http://127.0.0.1:53 0.0.0.0:* 1258277/named unix 3 [ ] STREAM CONNECTED 3645705 1258277/named unix 2 [ ] DGRAM 3645697 1258277/named
Are you using "named.service" or "named-chroot.service" when you use systemctl to start it?
It almost sounds as if you're not using the named.conf you think you're using.
ps -eaf | grep named output?
That being said. You supplied the output of "ip a" in another response. So, with those 2 lines commented out it should be listening on 127.0.0.1, 10.0.0.101, and 192.168.122.1 IPv4 addresses both tcp and udp. And it should be listening on tcp6 and udp6 :::53
Also, in your response to Tim you said......
"As my external IP is being supported by port mapping by router, all port 53 connects are routed to the internal address of 10.0.0.101:53 http://10.0.0.101:53."
Oh, so you don't have a"truly" public system. So, 108.220.213.121 is actually the IP address of your router.