Discussion Locked

Intranet Friendly Name

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running a Windows2000 Active directory and am in the process of setting up a simple intranet for employees.

My problem is I want to configure my DNS so I can use http://anyname instead of http://Computername to reach this internal site on my IIS.

2 replies

by rabbit_runner

Try this.

When you installed Active Directory, you had to give a DNS name to your domain. Something like..... mydomain.com OR mydomain.local

On your Intranet, this will be your web address for your domain.

Open your DNS appled and expand the tree on the left side. Find and highlight the DNS name for your local domain. Then on the right side, in a blank white space, right click and select Add HOST. This will bring up a dialogue box. In the window for the name place 'WWW' (withoug the quotes). In the IP address put the local IP address of the computer where your Intranet web site will be located. There is also a check box for creating a reverse look up entry. Put a check in that box, click OK or ADD and then close out your DNS applet.

At this point, your DNS is completely configured. However, each workstation (if they are Win2k or XP) will need to have their DNS cache refreshed. Windows 9x workstations should not need this. Also all workstations will need to have your domain DNS server listed (by IP) in the DNS settings on each workstation. If your are using DHCP, simply change the scope options and refresh the DHCP on each system. Otherwise you will need to visit each computer. To refresh the DNS cache on your workstation you can either re-boot the workstation, or from a command line (on each workstation) type...
ipconfig /flushdns THEN
ipconfig /registerdns

At that point, you can enter into your browser this URL... www.mydomain.com or www.mydomain.local

Hope this helps.

by cactus pete

Another suggestion is to add an alias, much the same way as the above [select alias instead of host].

Additionally, you should have all the clients set up to search the domain suffix that applies to your internal networks. If the FQDN for my box is:

machine.sub.domain.org

Then the search suffixes would be:

sub.domain.org and
domain.org

This allows you to not have to append the domains in the web address to resolve correctly [locally].

This discussion is closed to new replies.