Re: on to letsencrypt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 20/04/2021 07:31, Jack Craig wrote:


On Mon, Apr 19, 2021 at 3:11 PM Ed Greshko <ed.greshko@xxxxxxxxxxx <mailto:ed.greshko@xxxxxxxxxxx>> wrote:

    On 19/04/2021 03:18, Jack Craig wrote:
    >
    >     On Fri, Apr 16, 2021, at 10:56 AM, Ed Greshko wrote:
    >     > On 16/04/2021 17:19, Ed Greshko wrote:
    >     > > On 16/04/2021 10:35, Jack Craig wrote:
    >     > >> First I get my static IP from AT&T actually a block of eight addresses of which only the first do they agree to pass through.
    >     > >>
    >     > >
    >     > > BTW, if you are hosting the DNS server and if your DNS server has the IP address of 108.220.213.121 then
    >     > > this could be a problem.
    >
    > *
    > *
    > *would you expand on this comment? i think this is an issue,... thx..*

    I should have mentioned you should check your named.conf. By default it contains

    options {
             listen-on port 53 { 127.0.0.1; };


i had listen to localhost & external ip, trimmed to just localhost

             listen-on-v6 port 53 { ::1; };

    meaning it only is listening on the loopback interface.


i have uncovered some ns info issues with my ip provider, att, dns config issues...
working them out; you guys are a god-and tho! ;) thx!!!


Maybe you're not yet up and running, but FWIW, port 53 continues to show as
closed for both TCP and UDP at 108.220.213.121.

Also, FWIW, I just installed bind on a F33 test VM and changed named.conf to contain

options {
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { 2001:b030:112f:2::53; ::1; };

The VM is accessible via IPv6 but not IPv4.  And then running nmap from an external system.

PORT   STATE SERVICE VERSION
53/tcp open  domain  (generic dns response: NOTIMP)
| fingerprint-strings:
|   DNSVersionBindReqTCP:
|     version
|_    bind



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

_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux