0.2.5

• The installer's DNS check resolved through the local name service, which
  consults /etc/hosts first — and Ubuntu maps the machine's own FQDN to
  127.0.1.1. Any install whose hostname is also the server's hostname (a
  provider's default name such as srvNNNN.hstgr.cloud, or a box named after
  its domain) was rejected with "resolves to 127.0.1.1" despite public DNS
  being correct, leaving --skip-dns-check as the only way through.
• The check now resolves over DNS-over-HTTPS (Cloudflare, then Google). That
  is the right question to ask — what Let's Encrypt's resolvers see, not what
  this machine believes — and it stays dependency-free, since curl is already
  required while dig and host are absent from a minimal Ubuntu. It falls back
  to the local stack only when no public resolver answers, discarding loopback
  addresses that could only have come from /etc/hosts.
• Resolution moves to infra/lib/dns-resolve.sh with hermetic coverage in
  infra/tests/dns-resolve-test.sh, now part of the CI suite.