At 13:21 29/11/99 -0500, you wrote:
>Linux Gurus!
>
>I'm in need of some advice, and this is the best place I could think of to
>turn.
>
>Ok, here's the skinny:
>
>At my organization we are looking to implement both DHCP, and DNS (separate
>questions), and I have some concerns.
>
>DHCP:
>
>We have a large campus environment across several blocks, and most of the
>more remote locations are connected together by 10M ethernet via microwave.
>These links are pretty heavily utilized, so in our quest to implement DHCP,
>the thought has come up to locate multiple DHCP servers throughout the
>network. For example, putting a DHCP server in the most remote building, to
>service "just that building" and not having to propogate the DHCP traffic
>across the smaller network pipes. Additionally, we would have another DHCP
>server in the main data center to answer requests for the directly connected
>floors/buildings. All of our network hubs are 10M switched to the desktop,
>and for the most part a 100M collapsed backbone, with a few 10M backbone
>links.
>
>Will there be any problem with running multiple DHCP servers across the
>network? I'm not wanting to have to add specific MAC addresses to the
>server each time a new machine goes on to the network at any location. I'm
>thinking that a request would go out, and get 2 responses (albeit at
>slightly different times), and our traffic is still going to propogate over
>the slow links, regardless. Am I right?
Are all of your remote sites bridged or routed? If they are bridged then
route them. If they are routed then no problem, as DHCP requests are
broadcasts they will not naturally migrate beyond the local IP subnet
without direct router intervention.
>DNS:
>
>Currently we are usind NAT with a firewall, and our internal network is
>159.139.0.0 (which we don't own - the previous net admin just picked them
>out of a hat, and yes I am planning on replacing them with RFC1918
>addresses..) and we would like to set up our own DNS servers to resolve to
>some internal hosts, as well as provide name resolution for FQDN's out on
>the internet - sort of a mix of a internal DNS and an external DNS all in
>one "box". Would I have to have 2 seperate boxes? I also don't want our
>"internal" hosts FQDN's propogated outside of our network. Any suggestions,
>tips, etc?
You can easily do this with one box. There are many FAQs etc that cover
this. Basically you just need to setup the DNS servers (you will use more
than one won't you!) and tell them to forward queries for domains that they
don't know about to your ISPs DNS servers.
>Thanks for any suggestions, in advance!
>
>- Larry
Your welcome.
Graham....
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
