Hi Richard,
From: Richard [mailto:ratcheson@earthlink.net] [skip ssh1/ssh2 config]
Thanks John, I made that change. Do you have any idea why my default route has that strange destination? I went through Yast and by all that I can see it should not be that but should be the IP of my isp unless I am completely wrong. As I recall, it used to be the IP (24.233.51.9) that I get when the network is started. I did a whois on the name and got that it was available. Strange!!! ra
The fqdn (fully qualified domain name) of the mentioned ip-address is 'user-0ceico9.cable.mindspring.com'. Since 'route' has only a certain amount of characters available for each entry it just cuts the name after 'user-0ceico9.ca'. So nothing to worry there :o) If you don't want to use name-resolving with 'route', try 'route -n'. Try 'dig' or 'host' the next time to resolve an ip-address, 'whois' shows information about the regristration of a domain, not the hostname. regards, Stefan
On Tuesday 03 June 2003 22:25, Peer Stefan wrote:
Hi Richard,
From: Richard [mailto:ratcheson@earthlink.net]
[skip ssh1/ssh2 config]
Thanks John, I made that change. Do you have any idea why my default route has that strange destination? I went through Yast and by all that I can see it should not be that but should be the IP of my isp unless I am completely wrong. As I recall, it used to be the IP (24.233.51.9) that I get when the network is started. I did a whois on the name and got that it was available. Strange!!! ra
The fqdn (fully qualified domain name) of the mentioned ip-address is 'user-0ceico9.cable.mindspring.com'. Since 'route' has only a certain amount of characters available for each entry it just cuts the name after 'user-0ceico9.ca'. So nothing to worry there :o) If you don't want to use name-resolving with 'route', try 'route -n'.
To be precise, its his reverse, not his fqdn. -- _____________________________________ John Andersen
On Wed, 2003-06-04 at 01:25, Peer Stefan wrote: snip
The fqdn (fully qualified domain name) of the mentioned ip-address is 'user-0ceico9.cable.mindspring.com'. Since 'route' has only a certain amount of characters available for each entry it just cuts the name after 'user-0ceico9.ca'. So nothing to worry there :o) If you don't want to use name-resolving with 'route', try 'route -n'.
Try 'dig' or 'host' the next time to resolve an ip-address, 'whois' shows information about the regristration of a domain, not the hostname.
regards, Stefan, that's what I like about Linux and especially SuSE, I learn something new everyday. Now if I could only remember it all . . . .
Thanks for the response. Richard
participants (3)
-
John Andersen
-
Peer Stefan
-
Richard