Actually I would also be interested in such a setup, with separated DHCP/DNS since for a reduction in power consumption, and (even more important) for temperature reduction in server room, I run them on a low power NAS and I switch the main server (still not eduified) during night leaving only a working network for wireless connected laptops.
I see some complications in such a setup by the fact that workstations network configurations are distributed over DHCP. Cheers Giorgio On Fri, Mar 01, 2013 at 10:55:50PM +0100, RalfGesellensetter wrote: > Dear List. > > Mr. Ritter has a setting where dhcp & dns is done by a third party server > if I understand him correct (see below, German). Nevertheless there > is a tjener, and there is a gateway 10.0.2.1, but his problem is that > subdomains are not resolved (like sub.domain.no). Plain domains > (like domain.org) are resolved, however. Probably a temporary > problem, caused by third party software. > > Just in case it rings a bell of yours, please let him know. > > Cheers > Ralf > > ---------- Weitergeleitete Nachricht ---------- > > Subject: DNS-Problem > Date: Dienstag, 26. Februar 2013 > From: Ritter <[email protected]> > To: [email protected] > > Hallo Skoletuxe, > > wieder mal eine Frage aus Hessen, die bestimmt nicht sofort beantwortet > werden kann, aber ich bin optimistisch, dass mir jemand hier auf jeden Fall > eine Suchrichtung geben kann ;-) > > Mein tjener löst keine Namen mit mehr als 2 Bestandteilen auf. Bsp. erhalte > ich für > > traceroute to google.de (173.194.35.151), 30 hops max, 60 byte packets > 1 gateway.intern (10.0.2.1) 0.262 ms 0.470 ms 0.461 ms > 2 87.186.224.173 (87.186.224.173) 7.829 ms 8.683 ms 9.803 ms > 3 217.0.86.162 (217.0.86.162) 15.465 ms 15.471 ms 15.464 ms > 4 194.25.6.86 (194.25.6.86) 17.038 ms 18.155 ms 19.746 ms > 5 80.150.169.118 (80.150.169.118) 21.959 ms 80.150.169.114 > (80.150.169.114) 22.933 ms 24.062 ms > 6 209.85.248.12 (209.85.248.12) 22.670 ms 23.162 ms 209.85.254.108 > (209.85.254.108) 24.313 ms > 7 72.14.239.62 (72.14.239.62) 26.422 ms 10.481 ms 11.351 ms > 8 216.239.48.116 (216.239.48.116) 18.615 ms 20.381 ms 21.032 ms > 9 209.85.250.35 (209.85.250.35) 22.674 ms 23.491 ms 24.618 ms > 10 muc03s01-in-f23.1e100.net (173.194.35.151) 25.402 ms 26.638 ms > 27.617 ms > > .. aber auch: > > traceroute se.dyndns.org > se.dyndns.org: Der Name oder der Dienst ist nicht bekannt > Cannot handle "host" cmdline arg `se.dyndns.org' on position 1 (argc 1) > > DHCP und DNS macht bei uns ein TfK-Schulrouter. > > Die anderen Geräte im Netz haben damit kein Problem. > > Kann mir jemand etwas dazu sagen? > > Gruß > Thomas > > ------------------------------------------------------- > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > > -- Sysadmin SPSE-Tenero Ufficio: +41 91 735 62 48 Cellulare: +41 79 629 20 63 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
