Hi, On Mon, Jul 06, 2026 at 06:28:59PM +0200, Simon Hollenbach wrote: > have you seen this message from Chris aka OP?:
Yes. Did you? > On Sun, 5 Jul 2026 at 22:50, Chris Green <[email protected]> wrote: > > Simon Hollenbach <[email protected]> wrote: > > > Your domain also has an AAAA record, could it be that ssh is trying to > > > reach that instead of the IP you tested above? > > > You should be able to test this by forcing SSH to use IPv4, using `ssh > > > -4 isbd.biz`. Sprinkle in some `--verbose` flags if you still don't > > > understand what's going on, you can repeat `--verbose` or use multiple > > > `-v`s in a row, e.g. `ssh -vvv [...]` to increase verbosity further. > > > > > Brilliant! That's what was causing the oddity. > > > > I can fix the issue simply by adding an entry in ~/.ssh/config but I > > wanted to understand (better) what was going on. Note that OP says that the AAAA record is what "caused the oddity" but does not elaborate as to *why* that is so. I later followed up to say that *if* that's because the AAAA record is pointing at some other incorrect host then yes, that would be why. It looks like that is the case. > I think OP fixed the problem they were coming here for I don't think so, because the same AAAA record is there now as was there at the start of this thread. It very much looks like a totally unrelated host to what is at the A record. > it was a problem of SSH client preferring IPv6 and the server's daemon > apparently not listening on the advertised address. Incorrect. If that were the case then OP would have got a connection refused message. Furthermore there actually *is* something listening on SSH port on that IPv6 address. The fact that OP made the extremely unwise decision to disable host key checking, coupled with the hypothesis that the IPv6 address 2a00:1098:82::6:1 is *not* under control of the OP, explains everything that the OP has experienced. It's unlikely this thread would even exist if OP had used sensible SSH configuration, since their SSH would warn that they were trying to connect to a different host. > You might still help OP fix his server config, but I think the intial > question is resolved. While there could be further errors in OP's setup, the existence of an incorrect AAAA record is still the biggest known problem here. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
