Re: on to letsencrypt

[Jack Craig <jack.craig.aptos@xxxxxxxxx>]

On Tue, Apr 20, 2021 at 5:47 AM Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

On Tue, 2021-04-20 at 03:09 -0700, Jack Craig wrote:
> attached named.conf

It has the following lines in it:

  listen-on port 53     { 127.0.0.1; 10.0.0.1; 108.220.213.121; };
  allow-query     { localhost; 10.0.0.1; 108.220.213.121; };

Does your computer actually recognise one of its WAN ports as being
that IP?

Apparently not

I can do a telnet connect to IP for port 53 from 10.0.0.1 & localhost

10 .0.0.101 and the external IP do not connect

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.

t my external visible interfaces include only these

Changing those lines to listen and allow from "any" might make a
difference if your computer hasn't assigned 108.220.213.121 to one of
its interfaces.  At this time, since you're behind two routers, your
DNS server shouldn't be facing unwanted connections from anywhere else
to worry about.

The listen-on clause would be the interfaces it listens on, so your
computer's network has to have a port with that IP address.

I'm not sure if the allow-query is the same.  Whether it's allowing
queries coming in through that address, or allowing queries from that
address (i.e. the remote end making the query) and the remote end is
whatever *their* address is.

At the end you have:

  view "wan-view"
    {
        zone "linuxlighthouse.com" {
           type master;
           file "/var/named/linuxlighthouse.com.db";
           allow-update { none; };
        };

and so on...

But the supplied named.conf hasn't defined a "wan-view" acl, you've
only done "internals" and "slaves".


> registrar =  network solutions
> where they reference  => ns3.attdns.com & ws.llinuxlighthouse.com

I can see reasons to be your own webserver (e.g. not having to pay more
for someone else to do it, you can configure your server any that way
you like, etc).  But when you register a domain name, you're already
paying for someone to host your DNS records, and you don't have to do
anything extra.

Given these ACL's not employed  and questionable listen commands how should I

properly have configured this interface to provide external IP processing for primary dns service?

As you see , my guessing how to configure and make it work from looking at other configurations just isn't cutting it

Time to call in the 'pros from Dover'  (obscure movie reference)

visible interfaces

 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 50:65:f3:4a:ec:e5 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    inet 10.0.0.101/24 brd 10.0.0.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::15ef:5535:377f:e73f/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:4f:91:99 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:4f:91:99 brd ff:ff:ff:ff:ff:ff

tia,...

--

uname -rsvp
Linux 3.10.0-1160.24.1.el7.x86_64 #1 SMP Thu Apr 8 19:51:47 UTC 2021 x86_64

Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure