Internal DNS server for Intranet ONLY

[dneisler]

Can someone please help me with this? I dont have any experience setting up a Microsoft DNS server.

Here is what I want to accomplish:

Set up a Microsoft DNS server on an NT 4.0 server. The sole purpose of this server would be to translate my intranet, home.domain.com, to a local IIS server.

We are still going to use our ISP's DNS servers for our main name resolution. I plan on setting the new DNS server as the secondary DNS listing in DHCP.

Can someone walk me through the steps to create the records in DNS that will accomplish this?

 

[djhawthorn]

The way we do it is our NT Server does all DNS lookups for clients. We have a "fake" DNS hostmask (such as 'afakecompany.com') which our NT Server is the primary DNS Server for, then all our workstations have that as their primary DNS Suffix.

We then add the bulk of our servers, intranet sites, file servers etc. into that DNS zone on the server. DHCP then sets all clients to have the NT Server as the primary (and only) DNS Server. The NT server has itself and outside/ISP DNS servers listed, and staff can resolve names anywhere for anything.

The reason we used a fake DNS hostmask, was since our web servers are hosted by our ISP, we don't want to have to set "

http://www.companyname.com",

"ftp.companyname.com" etc. up in our DNS server, in case our ISP changes it on us. We'd prefer to resolve those "live" internet names off "live" internet DNS Servers.

Our intranet then is just accessed at

http://intranet

Nice and simple. Although you can still do it your way if you prefer. MCSE NT4/W2K