Printable View
Anyone up for more situations? I've got 4 more that I have to get worked out by Friday night. They are all concerning Win2000 Server. I'd LOVE more tips and hints if anyone is up for the challenge!! ;) Let me know, and I'll post them.
Thanks again for the help w/ offline files. That was awesome.
Em
What the hell, not like we got anything better to do. At least the first one was a decent question.
Thanks souleman, ok...here's the situation:
Brooks College is designing and implementing a new network that primarily consists of Windows 2000 Servers. They have purchased 10 server computers that will run Windows 2000 Server. They plan to set up DNS and DHCP servers for the network. Currently they have a small network that has two older servers. The college has hired you to work with their IT Department to plan and implement the new network.
Develop a document explaining to the IT Department how to plan the implementation of the DNS and DHCP servers. In that document address the following issues, as well as others you think are important:
In what order should the DNC and DHCP services be implemented? Should all the
services be implemented on one server or different servers and why? What security
issues should be addressed in the setup of these services?
The IT Department has set up a DNS server, but has no reverse lookup zone. This prompts serveral questions about DNS setup:
What is the purpose of a reverse lookup zone, and how can it be setup?
Can more than one DNS server be configured when the Active Directory is set up?
Can DHCP be configured to automatically update DNS records, and if so, how?
Well, that's one situation....haha. What do you think?
Em
That is way too much work for me, although it is not very difficlt. I will wait until other people answer most of the questions, and I will answer the ones nobody else does ;)
;) ok, thanks hon. :)
Ah...what the hell..
#1 - It doesn't technically matter which one is implimented first, but I would do the DNS server first because then once I configured the DHCP scope, I could define the DNS servers in the scope options and users wouldn't have to renew their address for the DNS settings to takes effect later. Again, it doesn't really matter technically if they they are on the same box, but I would separate them to add a little bit of fault tolerance (although if either one went down and you didn't have a backup, you would still be screwed. Security concerns -- Of course I would apply all the MS Service Packs ;) but I would also disable DNS zone transfers. Not to mention many other security things I would do like turn one of those win2k boxes into a firewall. But I will stick to the scope of the question.
#2 - Reverse lookup zones are for looking up FQDN's when inputing the IP address. It can be set up by defining in.addr.arpa records for each of the dns records in your forward lookup zone. Yes, more than one DNS server can be used with Active directory, in fact, that is the preferred method. DHCP can also update the DNS records by using the Dynamic DNS features in Win2k.
Phew...Hope I didn't skip anything.
Gosh iNVICTuS,
You just spit that out like it was nothing....I hope that I'm as smart as you one day!!! And what is FQDN's?
Thank you!!
Looks good to me invictus. Even remembered the service packs. You answered before I even got a chance to read the question ;)
I still think the company just wasted a lot of money on Win2kServer though...
fqdn.com
Fully Qualifyed Domain Name
thanks souleman
Thanks guys...
I am flattered
Sorry, wasnt around for the 1st question, whats the next? these sound a LOT like the microsoft MCSE exam questions... a WHOLE lot.
Avenger...are you stll here?
It's a Windows 2000 Server class that I'm taking, so that might be why they sound like the MCSE. The other situations are in General Chit Chat under ok...situation #3 and finally.....Situation #4. You'll see them...noone has responded to them though :(
I sure would appreciate any suggestions that you are willing to offer. thanks
Thats because they are really tough. Ill look for them , and put some thought into it, but they are AD questions and AD can be really tricky, no one wants to lead you down the dark path of wrong.
Get an HP A500 and put the latest bind on it (DNS), configure it for full-blown DNS as the primary for your domain. Set up another HP A500 that pulls from the first A500 as a secondary so you have a backup. Put both addresses in the client lists and on servers so that they hit the first one and if that doesn't work, it'll fail over to the secondary. On the secondary DNS server, also set up DHCP from www.isc.org, assign your scopes, IP pools, lease times, options, etc. Now you're ready to serve to the community.
OR
Get one machine, hook up bind that supports DDNS (dynamic) and then also hook up DHCP on the same machine so now you have a completely dynamic environment where printers can still be reached through names, regardless of whatever IP it got.