Home / server / Questions / 525545
Accepted
strugee
Asked: 2013-07-23 23:34:08 +0800 CST

Ping and traceroute can resolve my IP, but real clients (Apache, Adium, ssh) cannot

  • 772

I have set up my DNS with afraid.org. I have an A record ssh.strugee.net pointing towards 71.32.87.80. I do not have any AAAA records set up.

When I run ping ssh.strugee.net or traceroute ssh.strugee.net, they complete DNS resolution. However, when I ssh into ssh.strugee.net, DNS resolution times out. ping6 and traceroute6 fail similarly. If I directly put the IP that the DNS record points to, the operation completes.

Because of this I'm pretty sure the problem is that I don't support IPv6 somehow, but I don't know how to continue my diagnostics because I don't know how the network between me and my server is constructed, and I don't know how IPv6 and IPv4 operate in that network. Is there a generic way that I can find this out? How should I continue trying to resolve this issue?

It's worth noting that my ISP is CenturyLink and I have ran the check-ipv6 tests on the same ISP but in a different geographical location. It says that I have no IPv6 address. I use Google Public DNS and OS X. In the OS X DNS priority list, Google DNS IPv6 is first, followed by Google DNS IPv4, followed by the default set of DNS servers (CenturyLink's).

domain-name-system

1 Answers

  1. Best Answer

    If you're on a Linux or OS X system, you can do ssh -v [email protected] and see exactly why it's timing out.

    I doubt that it has anything to do with IPv6. It's probably to do with your client and how you're reaching the ssh daemon on the remote side. Clear your DNS cache and double-check all of your settings.

    • 1