Though that record does not exist anymore (if I check using a dns checker online, it also doesn’t find it)
I’ve read that let’s encrypt doesn’t use dns caching but I still get this result after 10 hours or so.
I also did a dns check (nslookup) on the server itself and it also didn’t find an AAAA record on that domain.
Any idea what’s going on, or what I am doing wrong?
Crap. I even used the dnschecker.org for propagation but apparently that’s isn’t full proof.
I’ll have to wait then. Thanks for your checker, I will use that to check during the day.
I'm not sure if waiting is the answer here. Surely, sometimes it takes a moment for the zone file edit to take effect, but I doubt TransIP takes more than 10 hours to do so.
I suggest you take another close look at your DNS zone file at TransIP to identify some other reason why the AAAA wildcard still exists.