On 5/31/23 18:45, Tim via users wrote:
On Wed, 2023-05-31 at 20:26 +0200, Peter Boy wrote:
> Did you really use
example.com <
http://example.com/>? That would
> never work.
No, I sanitised it. I've found, in the past, that exposing real
addresses gets it abused (extra spam and hacking attempts), since such
people harvest mailing lists and newsgroups.
Then that was a very misleading post... I assumed that it was some sort
of check that your DNS was functioning properly. But if it's actually
the domain you're trying to create the certificate for, then that makes
a very different situation. If you're making up names, you should at
least say that's what you're doing.