DNS issues; HELP

Viewing 1 post (of 1 total)
  • Author

  • raylward102

    Inherited a Server 2012 r2 domain (server 2008 functional level); It had 1 DC and 1 dead DC (dead dc, due to hardware failure).  I added a second DC (server 2008).  Clients cannot see domain computers listed under network, but can still access shares using names.  (YES; network discovery is turned on; YES clients have primary and secondary DN servers as the 2 live, functional servers).  When I run NSLOOKUP OurdomainName.Local, returns the name correctly and 4 IP addresses?? (was expecting 3).  3 of the address’s consist of the working master DC, dead DC, and newly added DC.  The unknown fourth IP, is a domain workstation on the network

    After combing through DNS records for on the master DC (server 2012 r2),  I’m left wondering about why I find 3 entries for 1 entry as a named workstation a record, 2nd entry as another named workstation record, and lastly, as a (same as parent folder) a record.   What does (same as parent folder) mean?  Why is this workstations IP appearing in my nslookups for the local domain?  Could this be why no one can see computers listed under network?  I haven’t pointed any computers to this but if nslookup is seeing it, could this be my problem?



    • This topic was modified 3 years, 2 months ago by biggles77. Reason: Remove the effing stupid formatting code on this suck software (and we though vB5 was bad.)
Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

The World’s Most Comprehensive Teams to Teams Migration Checklist

Whether you have just started thinking about migration or have already begun to move, our Microsoft Teams Migration Checklist can help guide you through the different phases for a Teams migration to another tenant.

This detailed six-step guide will walk you through key decision points while also providing more prescriptive best practice recommendations where appropriate.

Discover key insights for the following phases of a Teams migration: 

  • Discovery
  • Pilot
  • Planning
  • Communication
  • Execution
  • Validation

Sponsored by: