From owner-freebsd-questions@FreeBSD.ORG Thu Jun 30 00:42:18 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A21E16A41C for ; Thu, 30 Jun 2005 00:42:18 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: from mail2.securecrossing.com (209-254-39-195.ip.mcleodusa.net [209.254.39.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 3634A43D55 for ; Thu, 30 Jun 2005 00:42:18 +0000 (GMT) (envelope-from cblack@securecrossing.com) Received: (qmail 81539 invoked by uid 0); 30 Jun 2005 00:42:17 -0000 Received: from unknown (HELO localhost.localdomain) (cblack@securecrossing.com@127.0.0.1) by mail2.securecrossing.com with SMTP; 30 Jun 2005 00:42:17 -0000 From: Christopher Black To: Phil Cooper In-Reply-To: <16E46E74-7C0A-4F2D-A253-9F6E03335E67@gmail.com> References: <1120090939.920.20.camel@localhost> <16E46E74-7C0A-4F2D-A253-9F6E03335E67@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LvvdKQubIJUdlI+Np1Xb" Organization: Secure Crossing Date: Wed, 29 Jun 2005 20:42:22 -0400 Message-Id: <1120092142.920.25.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port Cc: freebsd-questions@freebsd.org Subject: Re: Ping and general network weirdness 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: Thu, 30 Jun 2005 00:42:18 -0000 --=-LvvdKQubIJUdlI+Np1Xb Content-Type: text/plain Content-Transfer-Encoding: quoted-printable XP can offer all the DNS it is aware of, but unless you updated a DNS server somewhere with fragile->192.168.1.204, it can't resolve. You have to do more than setting a hostname to make it resolve on the network. If you are obtaining the IP address on fragile dynamically anyway (via DHCP), you are going to have trouble keeping any DNS or host files up to date without getting into more complicated things like DHCP reservations or dyndns. If you haven't explicitly set fragile->192.168.1.204 in a DNS server, it won't resolve from any other machine unless you put it in that machines host file as well (windows has one, but the path eludes me right now). On Thu, 2005-06-30 at 01:23 +0100, Phil Cooper wrote: > As far as I know, not knowing much, doesn't the win XP box which =20 > connects to the net do all the DHCP and local DNS when XP's internet =20 > connection sharing is turned on? Which it is. It's at 192.168.0.1, =20 > which netstat is correctly reporting as the default gateway... >=20 > So is it a case of working out how to get XP to update things? >=20 >=20 > On 30 Jun 2005, at 01:22, Christopher Black wrote: >=20 > > It depends where fragile is mapped to the IP. If it's only in the =20 > > hosts > > file, the other machines have no way of knowing, and will probably =20 > > fail > > to resolve 'fragile' to an IP. If it's in DNS somewhere, you just =20 > > need > > to correct the DNS record. >=20 >=20 >=20 --=20 Christopher Black Chief Security Engineer Secure Crossing 22750 Woodward Suite 304 - Ferndale, MI 48220 Tel (800) 761-4299 | Direct (248) 658-6120 cblack@securecrossing.com | www.securecrossing.com --=-LvvdKQubIJUdlI+Np1Xb Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCwz/uAPxZlIbJ6AwRAlZuAJ9W6f5AiCT74oKS0HXSkrie/rA3dQCgghNz etzrZCpNj395tsWI1AO1yTs= =Z/sO -----END PGP SIGNATURE----- --=-LvvdKQubIJUdlI+Np1Xb--