Ping and general network weirdness
cblack at securecrossing.com
Thu Jun 30 00:42:18 GMT 2005
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
> connects to the net do all the DHCP and local DNS when XP's internet
> connection sharing is turned on? Which it is. It's at 192.168.0.1,
> which netstat is correctly reporting as the default gateway...
> So is it a case of working out how to get XP to update things?
> On 30 Jun 2005, at 01:22, Christopher Black wrote:
> > It depends where fragile is mapped to the IP. If it's only in the
> > hosts
> > file, the other machines have no way of knowing, and will probably
> > fail
> > to resolve 'fragile' to an IP. If it's in DNS somewhere, you just
> > need
> > to correct the DNS record.
Chief Security Engineer
22750 Woodward Suite 304 - Ferndale, MI 48220
Tel (800) 761-4299 | Direct (248) 658-6120
cblack at securecrossing.com | www.securecrossing.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20050629/50acbda6/attachment.bin
More information about the freebsd-questions