On 24/04/2021 10:29, Jack Craig wrote:
ok, done. now we have, ....
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
using 7 UDP listeners per interface
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
listening on IPv6 interfaces, port 53
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
listening on IPv4 interface lo, 127.0.0.1#53
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
listening on IPv4 interface eno1, 10.0.0.101#53
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
listening on IPv4 interface virbr0, 192.168.122.1#53
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
command channel listening on 127.0.0.1#953
Apr 23 19:25:59
ws.linuxlighthouse.com <
http://ws.linuxlighthouse.com> named[6483]:
command channel listening on ::1#953
And I see.....
Nmap scan report for
ws.linuxlighthouse.com (108.220.213.121)
Host is up (0.16s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
And I get
[egreshko@meimei ~]$ host
cnn.com 108.220.213.121
Using domain server:
Name: 108.220.213.121
Address: 108.220.213.121#53
Aliases:
Host
cnn.com not found: 5(REFUSED)
Which is correct since your named.conf currently contains
allow-query { localhost; };
So, at least your server is now contactable from the Internet. So you can go about adding
in the zones
you need as well as the access you want to allow.
--
Remind me to ignore comments which aren't germane to the thread.