Hi Andi, On So 27 Feb 2011 20:56:34 CET "Andreas B. Mundt" wrote:
What happens if I ask for the ltspserver's thin-client interface with associated name ltspserver? Well, I can add an A-record in the intern-zone that translates to 192.168.0.254. So far so good.
Maybe your problem does not need to be handled in DNS... If an ltspserver has two IPs... say... o 192.168.0.254 o 10.0.2.XX... Can thinclients in 192.168.0.0/24 ping the ltspserver's 10.0.2.XX IP address? If thinclients have a default route (i.e. route add default gw 192.168.0.254), they should be able to ping the other interface's IP in the ltspserver.
The only caveat I can think of: I am not sure, if the cross-NIC pinging works without /proc/sys/net/ipv4/ip_forward enabled in the kernel which we should definitely avoid on LTSP Servers).
Thus, if thinclients can reach the LTSP Server's external 10.0.2.XX-IP then you do not have to fiddle the LTSP Server's internal IP into GOsa². Just use the IP of the 10.0.2.XX-NIC in DNS.
Otherwise: how problematic is it introducing sub.intern domains into LTSP subnets of Skolelinux?
Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpa0ydHURho2.pgp
Description: Digitale PGP-Unterschrift
