-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've had this problem before, now I keep my hostname and fqhn on the local addy line like this.
127.0.0.1 kato.jeetkunedomaster.net kato localhost.localdomain localhost That way I don't have problems when I move from point to point where my IP# changes or I have the device down either. On Monday 30 December 2002 10:15 am, Wouter Lagerweij wrote: > Hi, > > I think something's wrong with hostname resolving, at least on my > machine, but maybe it's a cooker thing. > > I have the following configuration: > > host.conf: > order hosts,bind > multi on > > resolv.conf: > search lagerweij.com > nameserver 194.109.6.66 > > hosts: > 127.0.0.1 localhost.localdomain localhost > 192.168.1.2 om.lagerweij.com om > 192.168.1.1 ixolite.lagerweij.com ixolite > 192.168.1.3 angua.lagerweij.com angua > > Which should mean that a 'host om.lagerweij.com' resolves into > 192.168.1.2, since this hostname is in the hosts file, and the hosts > file is the first in the 'order' in host.conf. > Instead it resolves into my external ip address, 213.84.161.99, which > one would expect if the lookup was done through the nameserver. > (the same is true for both angua and ixolite) > > The reason I'm looking into this, btw, is that my machine seems to be > running a bit slower that I think is normal, and I heard gnome tends to > slowdown when there are lookup problems. > > Any ideas? > > Wouter - -- Jason Straight ICQ: 1796276 PGP: http://www.jeetkunedomaster.net/~jason/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iQCVAwUBPhCJLhFHZPcobeHxAQIFUQP/be5iiagWcC9WAyEAjmZlO4qczyM64UKe ILYDpcZrbjPUsSGBx0lKGicadIm21xqGO6d70G8bl6gefPGFqTjPHpSo71tfgIAL l+x4MJNIudlQmuy+RKYG6Z48zBOPqHXVpj6qNP4kaypYjV82huREesq4ZvT4cglW Lx8wmqFzaXs= =GpAV -----END PGP SIGNATURE-----
