Hi folks, have you seen this message from Chris aka OP?:
On Sun, 5 Jul 2026 at 22:50, Chris Green <[email protected]> wrote: > > Simon Hollenbach <[email protected]> wrote: [...] > > On Sun, 5 Jul 2026 at 21:40, Chris Green <[email protected]> wrote: [...] > > > If I log in with 'ssh 213.171.194.64' I, correctly, get prompted for > > > my local system's public key passphrase and I can log in successfully. > > > > > > However if I try 'ssh isbd.biz' I get prompted for "[email protected]'s > > > password" which doesn't exist and I can't log in. > > 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. I think OP fixed the problem they were coming here for, it was a problem of SSH client preferring IPv6 and the server's daemon apparently not listening on the advertised address. You might still help OP fix his server config, but I think the intial question is resolved. Ciao, Simon On Mon, 6 Jul 2026 at 16:54, Andy Smith <[email protected]> wrote: > > On Mon, Jul 06, 2026 at 10:41:36AM -0400, Greg Wooledge wrote: > > I'm slowly being convinced that name resolution is the real problem here. > > I agree, but in a much simpler way. > > OP has been repeatedly asked to confirm whether the IPv6 address in DNS > is actually pointing at the same host as the IPv4 address, but has not > yet confirmed. > > Someone (Vincent?) pointed out that the whois records for the two IP > addresses show very different entities. Still feasible for it to be the > same host, but looking suspicious by now. But for me, when I traceroute > to the IPv4 address it's about 5.6ms from me, whereas the IPv6 address is > about 0.6ms from me. > > The reverse DNS of the IPv6 address is caracal.mythic-beasts.com., which > bears nbo relation to OP and is a well-known hosting outfit in UK. > > So my conclusion is that two two addresses are in very different parts > of the Internet. Not 100% confirmed since one can easily introduce weird > routing and fake delays, but that would require some weird scheme, so > the most likely answer is it's simply a wrong IPv6 address. > > The reason why it always goes wrong when using host name is that Linux > prefers to use IPv6 addresses when it has both. > > Thanks, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting >
