Richard,
> I was going to try and set our internal e-smtih server to point to our real
> DNS server for resolution? What would this do to things? I was told by
> Charlie that this is a last case resort and is not recommended. And to just
> let e-smith resolve itself from it's root.hints file as it is quite capable.
>
> Or I guess we could set all clients to point to the real DNS server in the
> right place? But how do you make a DHCP assigned client use a specific DNS
> server? By default e-smith serves itself as the DNS to use?
In order for the DHCP server to pass out the info, the server must be
configured to use the other DNS server. I would suggest that you go through
the console configuration screens and put in the IP address of your "other"
DNS server as the "Primary DNS Server" (one of the last screens in the
console configuration process). The e-smith server will then use that one
for DNS, and will pass it out to clients via DHCP.
We tend to not recommend people have the e-smith server use another DNS server
purely because it introduces one more layer of complexity. (i.e. there is one
more machine upon which the e-smith server is dependent. We try to minimize
those.) However, it won't break anything to point your e-smith server to
another DNS server. You can see our concerns at:
http://www.e-smith.org/faq/#8q22
In your case, though, it sounds like it would be fine. (The other DNS server
is on a reliable Linux box, and more importantly it sounds like it is local.)
Regards,
Dan
--
Dan York, Director of Training [EMAIL PROTECTED]
Ph: +1-613-751-4401 Mobile: +1-613-263-4312 Fax: +1-613-564-7739
e-smith, inc. 150 Metcalfe St., Suite 1500, Ottawa,ON K2P 1P1 Canada
http://www.e-smith.com/ open source, open mind
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
