A lot of times I've seen questions about how this works when you have multiple nodes or a CDN, it can be quite tricky in theory if you have random IPs or several IPs. The way certbot works at least for non-DNS challenges is that it will hit a random server that it resolves to, you have no control over which one it hits. If certbot hits node 1 at first to tell it to create the well-known file, then checks node 2 or any other node, you will find auhorization fails.........

understanding /etc/aliases *remember to apply changes you need to run "newaliases" after editing /etc/aliases one thing I don't get is that it doesn't allow you to specify the whole e-mail address on the left-hand side eg: yourfullemail@domain.com: someotheremail@domain.com postalias: warning: /etc/aliases, line 109: name must be local (if you try the above) It works more like this: your........

Icouldn't understand why on one system it took a few minutes to get the SSHlogin prompt when connecting to other systems. The other systems all had the UseDNS parameter set to no, which almost always resolves the login prompt delay. The reason is Ubuntu and perhaps Debian and other distributions /etc/nsswitch.conf file Edit yours to have the "hosts" line like so (notice that files and dns are the primary resolution choice........

At this time we can't resolve Enom's website and all DNS requests to their 4 primary name servers are failing, although the hostnames themselves still resolve: Name Server: DNS1.NAME-SERVICES.COM Name Server: DNS2.NAME-SERVICES.COM Name Server: DNS3.NAME-SERVICES.COM Name Server: DNS4.NAME-SERVICES.COM Name Server: DNS5.NAME-SERVICES.COM You would really think Enom, bein........