https://bugs.contribs.org/show_bug.cgi?id=10300
--- Comment #43 from Dan Brown <[email protected]> ---
OK, so with the VM rolled back, letsencryptSSLcert enabled on the desired
hostname, and my pfSense box's IP address entered as "corporate DNS server" on
the SME box, host resolution for all three hostnames succeeds the first time.
Rolled back again, reconfigured again to use the pfSense as DNS, and ran
dehydrated -c; complete success. My pfSense box is configured to be its own
resolver, not merely a caching forwarder.
Rolled back again, reconfigured to use ISP's DNS, and ran dehydrated -c.
Again, complete success.
Rolled back again, reconfigured to use Google public DNS, ran dehydrated -c.
Once again, complete success.
This is looking more and more like a DNS issue on the SME end. We can
recommend a workaround of configuring a DNS server, but I don't think that's
the direction we really want to go.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
