ssh and dyndns.org query
Hi,
I have a dyndns.org dynamic dns address allocated to my router and ssh is working fine. Only problem I have is that the following syntax: Code:
$ ssh ****.dyndns.org -l andrew Code:
andrew@ilium~$ ssh -vvv i*****.dyndns.org -l andrew Andrew |
The problem isn't on the software side, it is with DynDNS. Either there is a delay in updating their DNS servers, or your router is not relaying the IP to the DynDNS site often enough (or at all).
|
Hi,
Thanks for the reply: Quote:
Logical when you think it through. If this is the case I need simply wait :-) Andrew |
There is the known_hosts file which stores past ssh transaction info
But perhaps this file doesn't store hostname/IP combo? (which if parsed [as maybe is yes indicated by the ssh_config] would send it over and over again forever to only the one IP that recorded when this new record was added to known_hosts You could make a backup copy of known_hosts then delete ~/.ssh/known_hosts Then you'd be starting anew (to discover if it then records/keeps the current IP) -- al@AB60R:/etc/ssh$ pwd /etc/ssh al@AB60R:/etc/ssh$ lsg h_co ssh_config next copy/pasted from /etc/ssh/ssh_config # Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. "2. user-specific" to me would mean the next file (known_hosts) in my /home al@AB60R:~/.ssh$ pwd /home/al/.ssh al@AB60R:~/.ssh$ ls known_hosts al@AB60R:~/.ssh$ in that known_hosts are any former ssh transaction I think (can't remember for certain) in the past I have deleted this known_hosts file and let it start over again (whenever some data in it had become outdated or in need of updating). I think (can't remember for certain) that once (a record of) a host gets in this file that such record then never changes (would always go for the same IP address again and again forever) when ssh, I think (not certain) it 1st checks this file -- even if you go to ssh to a *new one* (one that had not ever ssh'd to before) -- in the case of *new* is when a new record gets added to this file. -- Alan. |
Thanks acummings for your detailed reply. After having slept off a few frustrations with this matter I tested the whole setup again and the culprit was definitely a slow dyndns.org dns record. I tested this morning as follows:
1. Took note of the router's external IP address and checked that this tallied with the known_hosts file, which it did. 2. Rebooted the router and noted the new external IP address allocated by my ISP. 3. Used ssh -vvv on my dyndns.org address. The results showed that in this instance I logged on to the dyndns with the new IP number with no problem and there was also new entry in known_hosts with the same name but different IP address. Wonderful what 8 hours sleep can do :-) Andrew |
All times are GMT -5. The time now is 03:43 PM. |