This looks very much like the old https://dev.gnupg.org/T1447 where it looks like the fixes might have been applied only for SRV records, not the general case?
David Gray reported an issue with subject GnuPG 2.2.4 on Windows - problems accessing some HKPS keyservers. When I reproduce, using gpg --keyserver hkps://keys.mailvelope.com --recv-key $XYZ, my dirmngr log includes:
2018-01-23 21:28:10 dirmngr[70787.6] TLS verification of peer failed: hostname does not match 2018-01-23 21:28:10 dirmngr[70787.6] DBG: expected hostname: keyserver-prod.v3jierkpjv.eu-west-1.elasticbeanstalk.com
That hostname should not have been expected. DNS is untrusted (mailvelope.com doesn't appear to be signed, but changing behavior for that would be confusing) so the hostname to be verified should be the hostname which was supplied from a trusted source.