Nbadinova Mar 18, 2005   3:31 AM GMT

You can use the registry or group policy to fix many of the problems associated with a single name domain. Take a look at Microsoft Knowledge Base article 300684, "Information About Configuring Windows 2000 for Domains With Single-Label DNS Names" : http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

0 pointsBadges:

Sonyfreek Mar 28, 2005   9:20 PM GMT

Your DNS wasn't set up in the best of ways, but it does not have to be set up to an externally resolvable name. A single word for the domain name would work, as you have it, but it sounds like your DNS server wasn't set up properly when it was done. For example, DoD networks don't like to have their internal AD set up to something like dod.mil. They prefer ds.dod.mil, but it could be dod, if they chose to. You need to make sure that your DNS forwarders are set up properly resolve outside resources and that you can do a forward and reverse lookup on the internal domain. (Reverse lookup is not required, but makes troubleshooting easier). For forward lookups, do a "nslookup host" If this doesn't work, make sure your IP configuration is properly set up to whatever your DNS is set to (ex: domain) and that the name server is the proper IP Address. If you cannot resolve the nslookup, then your DNS server itself is not working/responding. You will probably be best to backup the DNS records, delete the forward/reverse lookup domains and start over. I typically create the forward domain first and immediately create the reverse (using the subnet IP Address, ex: 192.168.2.0). Then, as you create new records, your pointer records will automatically be created in the reverse domain. Good luck, Wayne

0 pointsBadges: