That’s handy – thanks!

Well, the good news is that I at least think I’m doing all the right things.

I’ll spin up a new VM tomorrow and start from scratch.

It’s literally just a VM hosting Apache and nothing else.

I mean, it could be… I’ll try it with a 128 char base 52 name and see what happens

Yes, exactly. Super weird, shouldn’t happen. I wonder if I have a compromised box somewhere…

The random name is not in the public log. Someone else suggested that earlier. I checked CRT.sh and while my primary domain is there, the random one isn’t.

As expected, it doesn’t show up. I had a couple of other subdomains configured before I switched to wildcard, but nothing matches the random one

Will do!

Shows up by name in the apache other_hosts…log, so yes

Yeah, this is interesting, I’ll dig more into this direction.

But the randomly generated subdomain has never seen a DNS registrar.

I do have *.mydomain.com registered though…hmmm

Nope

Yep. They show up in the other_hosts…log

I don’t think so? I have a letsencrypt wildcard cert, and reference that in the relevant .conf

R Pike is legend. His videos on concurrent programming remain reference level excellence years after publication. Just a great teacher as well as brilliant theoretical programmer.

Very cool, great work!

Worth noting about this approach is that the global list of subdomains is publicly searchable. So, you’ll see vulnerability and AI scans on those endpoints.

If that’s a concern for you, using path-based routing (e.g. Apache VirtualHost) allows you to use difficult to guess paths to your cloud.

Grow them… where?

…toe teeth!

Edit: my 100th comment!

Ewww…

Runbox (Norway) is a good option, good privacy protection and outside of EU chat control zone

Yep. Edited. Definitely autocorrect’s fault, not my morning brain fog.

No, actually you’re right. I meant wire guard.