At 05:18 AM 18/03/2004, you wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tony Bazeley wrote:
| Hello all,
|
| I have three machines using a static ip assignment
|     1. running smoothwall  as a net gateway (192.168.1.1)
|     2. XPpro
|     3 debian woody
|
| debian woody can ping the outside world using numeric addresses but is
| unable to resolve names, whereas the XP machine can do both.
|
| On the debian machine I have set up the gateway in /etc/network/interfaces
|
| and pointed to the name server by changing /etc/resolv.conf to
|     search HOME
|     nameserver 192.168.1.1
|
| and that the name server is used by checking that /etc/nsswitch contains
| the entry
|     hosts: files dns
|
|  From my rather bleary-eyed reading of the Network Admin guide at this
| time of night it should work - but it doesn't.
| Have I missed something?
|
| TIA
| Tony Bazeley

Are the machines in a domain called HOME?  The "dnsdomainname" command
without any parameters will tell you this. Either replace "HOME" with
the result of dnsdomainname or simply remove it, leaving "search" on a
line by itself.

- --
Andy Ruddock
- ------------
Senior Software Developer ([EMAIL PROTECTED])
GPG Key IDs : DSA/EIGamal=0x4E509520 RSA=0x5C38FD43 DSA=0x8B428591
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

Thanks very much to everyone for their responses.


As it turned out the problem was the first line in /etc/resolv.conf
        search HOME

which I've changed to simply "search" which now works well.

However I noticed that although HOME is returned by dnsdomainname on my machine as noted by Andy it seems that it is not recognised properly by the resolver.

Yet if I change the domain name to DEMILY in /etc/hosts then "search DEMILY" in resolv.conf works successfully.

It seems there is something significant about the domain name HOME.

Cheers
And thanks again
Tony Bazeley



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to