Re: on to letsencrypt

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

 



On Wed, 2021-04-21 at 11:47 -0700, Jack Craig wrote:
> perhaps in the meantime you could outline how to configure my setup
> for your simler,  /etc/hosts approach?

I suppose that before going into masses of technicalities, what does
your system actually *need* to do?

a) We know you're intending to serve pages from a webserver from your
computer, that doesn't require any of the DNS server malarkey you've
been trying to handle.  But will require passing HTTP and HTTPS
connections through from the outside world to your webserver.

b) You have a public domain name.  Your registrar can handle public
queries for its data, and doesn't need to know anything about your
internal LAN addresses.  Your local network can either use its own DNS
server, or you can use the hosts file, and it doesn't really need to
know anything about your public addresses.  Since you said you only had
one computer, then the hosts file is more than adequate for local
addressing queries on the same machine.

My /etc/hosts file has just these two lines in it:

  127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
  ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

They handle the localhost numerical IP and named addresses, and various
other aliases that some people expect to be used, but I've never seen.
The format is each line begins with a numerical IP address, the
associated hostname, then any extra aliases.  Any queries for the
numerical IP for any of those aliases will return the IP at the start
of the line.  Any queries for what name belongs to an IP will return
the first name in the list.

It could also include other local IPs and name:

e.g.  192.168.1.1    mycomputer  mycomputer.example.com
     192.168.1.254  myrouter    router.example.com

You don't have to do that, but if you want to simply associate
hostnames and IP addresses for other things on your LAN, you can do it
like that.

c) I don't know what you're doing with letsencrypt, to tell what it's
requirements will be.

_______________________________________________
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