• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 376
  • Last Modified:

Active Directory domain with no sign of DNS?

I am trying to help a friend of mine work on a non-profit's W2K3 DC.  Attempting to load AVG to clients via AD, however load fails.  Client reports inability to authenticate against DC.  Upon reviewing DC, AD is loaded and running as best as can be told, users seem to be authenticating against it as server also is used as file server for office and clients able to access authoritatively.  Here is the catch, no sign of DNS running on this server at all.  Have checked under:

1.  Services - only client service is displayed and running
2.  Server Manager - Only Domain Controller and File Server are displayed as rolls
3.  Event Viewer - no DNS log
4.  Add/Remove Components : DNS not checked or otherwise indicated as installed

First, how is this possible - has anyone else seen similar?  Second, how to bring DNS online, potential concerns, mitigations and expectations?
0
atlas_shuddered
Asked:
atlas_shuddered
1 Solution
 
dathhoCommented:
You've got to have DNS somewhere for AD to work.  What are the DNS entries set to on the server? (ipconfig /all) What is the response from nslookup commands on the server and clients?  Have you tried troubleshootinfg with dnslint?
0
 
Chris DentPowerShell DeveloperCommented:

> First, how is this possible - has anyone else seen similar?  

Possible but far from ideal and only partially functional. I imagine the clients are using NetBIOS to find the domain / DCs then NTLM to authenticate as and when they actively need to talk to it.

It is also possible the clients are using cached credentials and not actually authenticating against the domain at logon.

> Second, how to bring DNS online, potential concerns, mitigations and expectations?

Moderately easy, lets have a little check list:

1. Add the DNS Service
2. Create a new Forward Lookup Zone for the AD Domain
3. Ensure that the server points to itself (and only itself) for DNS servers in TCP/IP configuration
4. Restart NetLogon and run "ipconfig /registerdns" on the DC. Ensure that an _msdcs folder is created under the Forward Lookup zone after this.
5. Run DCDiag and NetDiag to verify the state of the server and AD.
6. Change client TCP/IP settings to point at the DC for DNS (again, and only the DC)
7. Check event logs on the client for errors

HTH

Chris
0
 
AmericomCommented:
If your AD is not relying on external DNS or other 3rd party DNS like unix, then you can try remove DNS and reinstall DNS services.
If your DNS, you must have a Host, Name Server, and SOA  record of your domain controller.
You should be able to run NSLOOKUP the domain name as well as the domain controller server name to get the IP of your domain and vice versa. Just make sure your IP configuration for your DC is pointing to itself as the preferred DNS.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
atlas_shudderedSr. Network EngineerAuthor Commented:
dathho

I'm going to try and answer all three of you here.  Sorry for the delayed response.

ipconfig/all - The server is referencing the DG as its DNS server.  That being said, it would be referencing an ISP indirectly for DNS.  Clients, I have been told, are definitely referencing ISP DNS.

nslookup - returns same basic information

dnslint - going to hold on this for the time being

Chris-Dent

I was thinking the same thing may be happening - possibly pulling from cached DNS to keep AD running?  

The clients would have to be authenticating against AD in order to still access the files on the DC yes?

Regarding your directions.  Sounds straightforward, however I am unfamiliar with this type of situation so would like to clarify a couple of points -

First, these directions will install DNS and then link it back to AD after it is up and in a stable state (i.e. created as a primary DNS server, forward lookup zone to AD is established, etc.)?

Second, what is the likelihood that AD and therefore the server itself will crash during this procedure?

Third, in the event of a crash, is it possible to rebuild the box, re-install DNS and configure and then overlay or restore AD to the box?

Americom -
DNS isn't running on the box at all.  Only service registered anywhere on the machine as DNS is the DNS Client service itself.

Thanks for the input so far guys.
0
 
Chris DentPowerShell DeveloperCommented:

> I was thinking the same thing may be happening - possibly pulling from cached DNS to keep AD running?  

Only works if there's a server answering authoritatively for the zone which doesn't appear to be the case :)

> The clients would have to be authenticating against AD in order to still access the files on the DC yes?

Yes, using NTLM and server level authentication rather than Kerberos and domain level authentication.

> First, these directions will install DNS and then link it back to AD after it is up and in a stable state
> (i.e. created as a primary DNS server, forward lookup zone to AD is established, etc.)?

Yes, although the instructions have you test and verify a number of times to verify it is behaving after each major step.

> Second, what is the likelihood that AD and therefore the server itself will crash during this procedure?

In my opinion, none at all. We're not doing anything remotely destructive, only adding in missing services.

> Third, in the event of a crash, is it possible to rebuild the box, re-install DNS and configure
> and then overlay or restore AD to the box?

You need a backup of the System State. That will include DNS in it's current state (including service state). The best we could do is drop back to that in the event of total failure. I do advise you take a backup regardless of my opinion on the risk level above. Better safe than sorry and all that :)

Chris
0
 
atlas_shudderedSr. Network EngineerAuthor Commented:
Chris

Thanks for the reply.  We've already got a backup, just wanted to verify those points prior to trying.

Wish us luck.

Cheers

J
0
 
atlas_shudderedSr. Network EngineerAuthor Commented:
Cheers and thanks again for the input.
0
 
Chris DentPowerShell DeveloperCommented:

Good luck :) You know where we are if it doesn't play the game :)

Chris
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now