On Tue, Apr 20, 2021 at 4:16 PM Ed Greshko <ed.greshko@greshko.com> wrote:
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


named.service

it?
ps -eaf | grep named  
named    1263562       1  0 13:59 ?        00:00:05 /usr/sbin/named -u named -c /etc/named.conf -4
root     1280487  311233  0 19:09 pts/0    00:00:00 grep --color=auto named

 
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>."

what i wanted to mean was all 108.220.213.121:53 go through router pair and are mapped into 10.0.0.101:53
ports 80, 443, & 53 are port forwarded to 10.0.0.101


Oh, so you don't have a"truly" public system.  So, 108.220.213.121 is actually the IP address of your router.

 
no, my router has its own ip

  does the following 'ping path' help me explain??

10.0.0.101        ws server (me)      2 packets transmitted, 2 received, 0% packet loss, time 1027ms
10.0.0.1          netgear gw          2 packets transmitted, 2 received, 0% packet loss, time 1002ms
192.168.1.254     router att          2 packets transmitted, 2 received, 0% packet loss, time 1001ms
108.220.213.126   att gw              2 packets transmitted, 2 received, 0% packet loss, time 1002ms

108.90.204.76     att subnet (local)  2 packets transmitted, 2 received, 0% packet loss, time 1002ms
108.90.204.1      att subnet (remote) 2 packets transmitted, 2 received, 0% packet loss, time 1002ms
68.94.156.8       att dns (pri)       2 packets transmitted, 2 received, 0% packet loss, time 1002ms
68.94.157.8       att dns (sec)       2 packets transmitted, 2 received, 0% packet loss, time 1001ms







--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure