From owner-freebsd-questions@FreeBSD.ORG Sat Apr 10 14:54:28 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9C38106564A for ; Sat, 10 Apr 2010 14:54:28 +0000 (UTC) (envelope-from walterk1@earthlink.net) Received: from pop-borzoi.atl.sa.earthlink.net (pop-borzoi.atl.sa.earthlink.net [207.69.195.70]) by mx1.freebsd.org (Postfix) with ESMTP id B5A2E8FC18 for ; Sat, 10 Apr 2010 14:54:28 +0000 (UTC) Received: from user-0c6sn0e.cable.mindspring.com ([24.110.92.14] helo=[192.168.0.100]) by pop-borzoi.atl.sa.earthlink.net with esmtp (Exim 3.36 #1) id 1O0c4p-0005MW-00 for freebsd-questions@FreeBSD.org; Sat, 10 Apr 2010 10:54:27 -0400 Message-ID: <4BC0911E.2090703@earthlink.net> Date: Sat, 10 Apr 2010 09:54:22 -0500 From: Walter User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: host & dig X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2010 14:54:28 -0000 A previous question to the List on how to get an IP address from a host speicific URL yielded the helpful responses of "host" and "dig." These (seemed to) work fine. Well, just now I got a chance to try it out on a tiny server I have at someone else's house, and on another network. I used telnet to connect to 68.204.xxx.xxx it tells me I've connected to xxx.xxx.204.68.cfl.res.rr.com. (backwards, right?), then I log in. After user/pass entry, it says connected from "user-yyyyyyy.cab" (replaced seemingly random name with "yyyyyyy" in case it's not transient) My external IP here is 24.110.nnn.nnn The issue: When I use either "host" or "dig" to give me the IP address from "user-yyyyyyy.cab", they tell me: 208.68.zzz.zzz (Ping gives the same.) So, I'm still at a loss, I think, to know the originating IP. Should a firewall rule blocking 208.68.zzz.zzz actually operate against 24.110.nnn.nnn? I'd STILL like to know the true source IP to be able to connect back to it. TIA. Again, please respond directly to me (as well as to the List) because I'm not subscribed. Walter