http://bugs.skolelinux.org/show_bug.cgi?id=1439
--- Comment #7 from Petter Reinholdtsen <[email protected]> 2010-02-05 13:01:26 --- I tested on two laptops. The main-server+thin-client-server laptop only have one network card, so I made interface dummy0 have 10.0.2.2, and eth0 use 192.168.0.254 to simulate the thin client network. When I boot a thin client in this setup on the 192.168 subnet, its /etc/resolv.conf lists 192.168.0.254 as its DNS server, and DNS lookups work as they should. I tried both host www 192.168.0.254 - Works as it should host www 10.0.2.2 - fails The failing host call fail with host stating that the reply came from an unexpected source. So this make me wonder how the thin client Ole Anders looked at could have 127.0.0.1 listed as the DNS server on the booted client. Ole Anders, can you check again? -- Configure bugmail: http://bugs.skolelinux.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are watching all bug changes. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
