Using No-IP to Access my Home Network from Abroad

[BillytheImpaler]

I've got a home server running Linux that I'd like to contact from outside my home network for the purpose of remote administration. I have DSL service with a dynamic IP address that changes a few times per day. I connect via ssh which, for the purposes of discussion, uses port 22. In my router running DD-WRT I set it to forward port 22 to its local IP address which we'll call 192.168.0.100. I was able to point ssh to it by knowing the external IP for the moment, let's say 34.45.126.99 like so:
ssh -p 22 [email protected]

I'd like to be able to use no-ip so that I don't have to know the dynamic IP address any more. Now I'd like to be able to do something like
ssh -p 22 bti@http://billsserver.no-ip.org

I might have misconfigured it or something, but I can't access it from the URL no-ip gave me. I installed the no-ip client on the machine and configured it. I guess I just don't know what to put in the config. At no-ip's web site in the profile it asks for its IP address and I'm not sure if I should be giving its local IP or my modem's current external IP.

Long story short, does anybody have any good setup guides or know-how in this area that can help? I've never really used no-ip's service before.

Am I going about this all wrong?

Thanks in advance.

 

[BillytheImpaler]

I don't have any idea what sort of settings I need to change in the router. When I get home tonight I'll scout for DDNS-related settings and ask what to do here.

Thanks thus far.

EDIT: If it might matter, I always get the following when trying to connect:
bti@TCB247:~$ ssh -p 22 [email protected]
ssh: connect to host billsserver.no-ip.org port 22: Connection refused

 

[BillytheImpaler]

I did definitely enable the port forwarding. If I hadn't I wouldn't ever have been able to ssh into it when I had the current external IP address, no?

I haven't touched iptables on it. It's just a wee MythTV backend. I'd like to be able to check up on it when I'm away.

 

[BillytheImpaler]

When I'm at home this evening I'll have better, more specific information for you. I'll see what I can find in the router, the no-ip profile page, and the machine's configuration file.

 

[BillytheImpaler]

billsserver is not the actual name. I'm keeping that private, just like the forwarded port.

Pretty much the wh0ole router config is stock DD-WR v23 PS2 except for the root password, wireless setup, a few forwarded ports, and static DHCP for most of my machines.

 

[BillytheImpaler]

TCB247:~ bti$ ping billsserver.no-ip.org
PING billsserver.no-ip.org (34.45.126.99): 56 data bytes
^C
--- billsserver.no-ip.org ping statistics ---
41 packets transmitted, 0 packets received, 100% packet loss

I reconfigured the server to be sure that I put everything right in the config file. I ssh'd into my workstation at the office and, as above, tried to ping it. The hostname to IP resolved correctly so it would appear that no-ip has their stuff right, at least based on what I entered in the web host configuration. I got tired of waiting for it to timeout so I ctrl C'd it.

When I try to ssh I get:
TCB247:~ bti$ ssh -p 22 [email protected]
ssh: connect to host billsserver.no-ip.org port 22: Connection refused

When I try to do it the old fashioned way, using the direct IP and port, it answers ping and allows ssh access.