-----Original Message----- From: James Knott [mailto:james.knott@rogers.com] Sent: Thursday, November 04, 2004 7:17 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Determing IP address
How can I determing the IP address of a server, when I use
Paul Ryan wrote: ping and then
the ftp:// address I get the response unknown host.
????
How can you ping, if you don't know the IP or host name.
What application are you using? What happens if you use the ftp command.
I think the problem is that the name can't be resolved (IE Paul has a host name. Just no IP). ping SOMEHOST and ftp://SOMEHOST both return unknown host, so without knowing the IP address off the top of your head or being able to go to a box that can reach that host via its name, your stuck. -Chris Kwasneski System Engineer Yuma Proving Grounds, AZ
On Thu, 2004-11-04 at 09:35, Kwasneski, Christopher D (Northrop Grumman) wrote:
-----Original Message----- From: James Knott [mailto:james.knott@rogers.com] Sent: Thursday, November 04, 2004 7:17 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Determing IP address
How can I determing the IP address of a server, when I use
Paul Ryan wrote: ping and then
the ftp:// address I get the response unknown host.
????
How can you ping, if you don't know the IP or host name.
What application are you using? What happens if you use the ftp command.
I think the problem is that the name can't be resolved (IE Paul has a host name. Just no IP).
ping SOMEHOST and ftp://SOMEHOST both return unknown host, so without knowing the IP address off the top of your head or being able to go to a box that can reach that host via its name, your stuck.
-Chris Kwasneski System Engineer Yuma Proving Grounds, AZ
Don't you need to use the fully qualified domain name to determine IP of the host? Example: carlh@linux:~> ping google ping: unknown host google carlh@linux:~> ping www.google.com PING www.google.akadns.net (216.239.41.104) 56(84) bytes of data. 64 bytes from 216.239.41.104: icmp_seq=1 ttl=241 time=42.1 ms 64 bytes from 216.239.41.104: icmp_seq=2 ttl=241 time=39.5 ms --- www.google.akadns.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 39.569/40.876/42.183/1.307 ms
On Thursday, 4 November 2004 16.24, Carl Hartung wrote:
Don't you need to use the fully qualified domain name to determine IP of the host?
Example:
carlh@linux:~> ping google ping: unknown host google
carlh@linux:~> ping www.google.com PING www.google.akadns.net (216.239.41.104) 56(84) bytes of data. 64 bytes from 216.239.41.104: icmp_seq=1 ttl=241 time=42.1 ms 64 bytes from 216.239.41.104: icmp_seq=2 ttl=241 time=39.5 ms
Now try again, and add the line search com in /etc/resolv.conf (removing any other search line you may have there of course)
On Thu, 2004-11-04 at 10:35, Anders Johansson wrote: <snip>
Now try again, and add the line
search com
in /etc/resolv.conf
(removing any other search line you may have there of course)
Hi Anders! What an honor! <Big Grin> I should know better. Trying to respond to posts when I'm multi-tasking and have a lot of distractions here in the background seems to always turn into a "two steps forward, one step back" proposition... and my five year old isn't even home from school, yet! So, I appreciate your response. My resolv.conf is the temporary one created by dhcpcd, so I'd have to dig elsewhere to modify it. Is the principal benefit that one need not prepend "www" or append "com" to discern a host's IP address? regards, - Carl
On Thursday, 4 November 2004 17.20, Carl Hartung wrote:
On Thu, 2004-11-04 at 10:35, Anders Johansson wrote: <snip>
Now try again, and add the line
search com
in /etc/resolv.conf
(removing any other search line you may have there of course)
Hi Anders! What an honor! <Big Grin>
heh
I should know better. Trying to respond to posts when I'm multi-tasking and have a lot of distractions here in the background seems to always turn into a "two steps forward, one step back" proposition... and my five year old isn't even home from school, yet!
So, I appreciate your response. My resolv.conf is the temporary one created by dhcpcd, so I'd have to dig elsewhere to modify it. Is the principal benefit that one need not prepend "www" or append "com" to discern a host's IP address?
You asked a question, I answered it. You were wondering why you couldn't just "ping google", and the procedure above attempted to show that when you use a simple hostname, the resolver will try to append the domain in the "search" directive in resolv.conf. If you put "search google.com" in resolv.conf you could do "ping www" and it would ping www.google.com for you
On Thu, 2004-11-04 at 11:32, Anders Johansson wrote: <snip>
You asked a question, I answered it. You were wondering why you couldn't just "ping google", and the procedure above attempted to show that when you use a simple hostname, the resolver will try to append the domain in the "search" directive in resolv.conf. If you put "search google.com" in resolv.conf you could do "ping www" and it would ping www.google.com for you
I did a quick "info resolv.conf" after our last exchange, so I actually understand what you've said here. That'll probably last for a day or two. I honestly don't know how you keep all this stuff so well organized and updated in your head, Anders. It's absolutely amazing. Ever thought about leaving your brain to science? ;-) Thanks for the feedback & take care! - Carl
participants (3)
-
Anders Johansson
-
Carl Hartung
-
Kwasneski, Christopher D (Northrop Grumman)