×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Internal DNS on Win2K server not working

Internal DNS on Win2K server not working

Internal DNS on Win2K server not working

(OP)
I obviously have not configured my DNS correctly, can someone give me a forinstance of the forward and reverse look up zone files in Windows 2000 server DNS

3 node DOMAIN, WIN 2 K DC, WIN 2 K server- Exchange - web site,

Mail site has domain name on my ISP, others not registered, don't want to either.

Help please

Thanx,

Bruce

RE: Internal DNS on Win2K server not working

Ok I would start by checking the event viewer. Look for Netlogon errors and see if they are dns related.  I will assume you have Active directory installed, and you used the active directory installation wizard to setup dns?
This should setup everything for you.  You only will need a foreward zone.  I assume your ISP is hosting DNS for you and pointing to your mail/web servers.  If you don't have AD installed It would be benificial to do so. This would automatically setup dns.  I would remove the gateway address from your NIC on the server and dns enties.  This way your server when installing AD won't install root hints and try to get authorized for Dynamic updates.  This method will install your DNS as a root server or "." record in your foreward zone.  NOTE: This server will not get external DNS resolution with this method, if you want internet resolution you will have to add this final step.  Delete the "." in the foreward zone. goto the dns forewarder window pane and refresh, add the dns servers here.  don't forget to put back your gateway in the nic setup.

RE: Internal DNS on Win2K server not working

(OP)
Thank you eightball.

This is a pretty dormant domain, and I would like to uninstall and reinstall AD on the DC.  Can I do this without blowing myself up?  If I can, can you point me to the snap-in that will help me accomplish this?

Thanx,

RE: Internal DNS on Win2K server not working

bhb3881dmb,

"Can I do this without blowing myself up?"

I'm not sure what you mean by this statement, but if you remove AD, you have done just that, it's gone.  

To uninstall Active Directory, you must demote the Domain Controller back to a Member Server.  To do this, go to the Run line and type DCPROMO...and then follow the wizard.

Keep in mind, this will be a problem if your other Servers are members of your domain...


Patty

RE: Internal DNS on Win2K server not working

(OP)
GrnEyedLdy,

Thanx, I guess my next question then, if I remove my other 2 systems from this Domain, then DCPROMO to demote the DC, then DCPROMO to re-AD the system, (will this rerun the DNS portion), then join the other 2 systems back to the Domain.  Will this clean up the Domain/DNS environment?

Thanx,
Bruce

RE: Internal DNS on Win2K server not working

Do not remove AD it will delete your user accounts SID history, etc..  If you have no users or groups knock yourself out.  Also if your running a mixed mode network, nt 4.x or there is another AD in the forest you will experience a melt down.  Unplug the ethernet adapter to other DC or AD.  Otherwise it will hose the Ad and DC.

RE: Internal DNS on Win2K server not working

(OP)
A little insight on my DNS, here is some exported data:

This is the export of the forward lookup zone:

Name         Type         Data
(same as parent folder)         Start of Authority         [1], webntdom.keane-nne.com.,
admin.keane-nne.com.
(same as parent folder)         Name Server         webntdom.keane-nne.com.
(same as parent folder)         Host         64.61.40.100


This is the error that I get when I run DCDIAG:

   Testing server: Default-First-Site-Name\WEBNTDOM
      Starting test: Connectivity
         WEBNTDOM's server GUID DNS name could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (fff164d9-ab58-4add-80d6-2bda3ac870ba._msdcs.keane-nne.com) couldn't
         be resolved, the server name (webntdom.keane-nne.com) resolved to
the
         IP address (64.61.40.100) and was pingable.  Check that the IP
address
         is registered correctly with the DNS server.
         ......................... WEBNTDOM failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\WEBNTDOM
      Skipping all tests, because server WEBNTDOM is
      not responding to directory service requests

   Running enterprise tests on : keane-nne.com
      Starting test: Intersite
         ......................... keane-nne.com passed test Intersite
      Starting test: FsmoCheck
         ......................... keane-nne.com passed test FsmoCheck

C:\>


Thanx,

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close