A n00b and her ssh. Help?

[tarahmarie]

Hrm. Can you post the output of this:

sudo lsof -i

The relevant part of the list:

sshd      23927       root    3u  IPv4 438393      0t0  TCP *:22255 (LISTEN)
sshd      23927       root    4u  IPv6 438395      0t0  TCP *:22255 (LISTEN)

And that's the weird part. I know sshd is listening on the correct port.

[tarahmarie]

Interesting. It would seem that the problem isn't with my SSH setup at home; it's with my dynamic DNS provider. I have OpenDNS set up with my home network. My ddclient is properly updating my account at OpenDNS; IP address changes happen instantly. I have pointed my subdomain name (the one I chose to represent my home network) to the OpenDNS IP address.

When I hit my home IP address directly, all is well. When I try to hit it through the FQDN as represented by OpenDNS, nada.

What might be the problem? Obviously I need to figure it out before the next IP address switch at home, thanks to my Comcastic ISP.

[CharlesA]

I didn't think openDNS did dynamic DNS.

I've used dyndns.org for that.

Does the FQDN resolve the the correct ip address?

[CharlesA]

I didn't think openDNS did dynamic DNS.

I've used dyndns.org for that.

Does the FQDN resolve the the correct ip address?

[tarahmarie]

I didn't think openDNS did dynamic DNS.

I've used dyndns.org for that.

Does the FQDN resolve the the correct ip address?

According to http://www.************/find_ip_addr..._a_website.php, yes. It resolves to one of the two IP addresses provided by OpenDNS (the one I pointed it to in the zone file); now, I am still a noob at this sort of configuration, so it's possible that I am overlooking something key. Still, the whole point of setting up a FQDN is to have a standard entry in all my putty/winscp/connectbot/whatever-uses-a-key apps.

I am under the impression that you set up a domain (or subdomain, whatevs) to point to an IP address provided by a dynamic DNS provider. They then forward that FQDN to the IP address provided by whatever DD client you're running (and I'm running ddclient, which is configured properly and reporting my correct IP address to OpenDNS). Is this the case? If so, is the forwarding process stripping the headers or something?

[CharlesA]

Try using dig to do a lookup of the domain names.

dig www.somedomain.tld

[tarahmarie]

Try using dig to do a lookup of the domain names.

dig www.somedomain.tld

I did, but it only says that my domain name is pointed to the correct IP. Why use a different tool to do what I already know?

[CharlesA]

Something isn't working right, as you said you can connect fine if you are using the ip address, but not if you use the domain name.

If the domain name resolves to the correct IP there shouldn't be a problem.

[tarahmarie]

Something isn't working right, as you said you can connect fine if you are using the ip address, but not if you use the domain name.

If the domain name resolves to the correct IP there shouldn't be a problem.

I have a support ticket in to OpenDNS now to see why my FQDN resolves to the correct IP address but does not permit me to ssh into my home box.