> On the LTSP server, there is two ethernet card. One of them is on the local
> network and has an IP 192.168.0.1, the other is connected to the internet
> through ADSL modem.
>
> On the TCP/IP settings of the Windows Terminal Server DNS setting is
> 192.168.0.1 which is the interface that bind is listening. (On the wan
> interface bind is not listening and is protected by firewall).
>
> My LTSP server's and client resolve.conf files are same
>
> nameserver 192.168.0.1
> search something.org
>
What is "Windows Terminal Server DNS"? Did you mean Linux Terminal Server?
I must not have a clear understanding of your enviornment.
LTSP server has 2 NICS, one of which is 192.168.0.1 (true/false)?
LTSP server is running named (true/false)?
LTSP server is running dhcpd (true/false)?
LTSP terminals boot and run ok (true/false)?
If you are running named on LTSP server, you have also successfully
built a configuration for something.org (true/false)?
What nodes/hosts are having the DNS lookup issue?
Does the LTSP server also have this problem?
Also, please identify what version of linux and ltsp you are using.
This still sounds like a resolv.conf problem at some level, unless named is
not configured corectly.
Are you willing to post (or email me):
lts.conf, named.conf, dhcpd.conf & /etc/hosts
On the LTSP server, run then following and send the output:
host -v [terminal-name]
host -v [terminal-name].something.org
-christoph
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
