Networks

I think you should follow a hierarchial DNS design (Which is the current, modern method of Active Directories and other directory services. If u ever decide to go to Win2K AD, you'll thank yourself for implementing a hierarchial, logical design.

Your answer will depend on your administration. Who are your DNS administrators and what do they have authority over? If you have fifty DNS administrators, and each one has authority over a state, then one per state would make sense. You would delegate DNS authority to whatever level you needed, state, region within a state, or site.

You should make a standard for naming now and enforce it throughout all 20000 sites. Ideally in your standard name it will tell you location and type of equipment. You can include any information you might need, though, such as date acquired, or date warranty expires, whatever you need. For instance:

somewhere.com - Root
fl.somewhere.com - State
abcd.fl.somewhere.com - Site or Region
R050301.abcd.fl.somewhere.com - Router, code 05=7513 Cisco model, 0301 = Acquired March, 2001
S021200 - Server, code 02=Compaq 8000, 1200=Acquired December, 2000.

I do not recommend using CR7513. Rather, use a code that means Cisco Router model 7513. You need info that is meaningful to your company, but not the rest of the world. If the DNS name is available on the Internet, you don't want to blatantly advertise the type of equipment.

This question was closed by the author