DNS Setup … very poorly done, and now need some help re-doign it

Amfony
pts.
Tags:
Active Directory
DNS
Microsoft Windows
I have come across a DC running MS DNS. this server has been experiencing group policy issues, now i investigated and came across some certain problems. the domain name is a single name "domain" .. not a FQDN as in "domain.Work" the dNS has no root zone, or domain. (this i dont know if its a problem or not - i think it is) whilst in nslookup - i cannot resolve the domain name "domain". However can resolve the name "domain.". What should i be doing next? and how do i come across information to help me witht this? How can i iron out all these issues? thanks guys any questions i can gointo more details ... thank you
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

You definately have a problem. You will need to rename to domain to something more suitable, like mycompany.local or anything with an extension. If you are using Windows 2003 you may be able to utilize the domain name change tools to work it out. However, if you have Exhcange installations or child domains this will not be very effective. Rebuilding the domain will be the only other recourse.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Nbadinova
    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:
    report
  • Sonyfreek
    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:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: