Forum Discussion

piotr's avatar
piotr
Copper Contributor
Feb 21, 2018

Re: Problem to setup DNS server on Windows Server 2016

Well, I dont have:

 

Forward Lookup Zones/ad.komplex.info.pl/_msdcs/dc/_sites/Default-First-Site-Name/_tcp
Forward Lookup Zones/ad.komplex.info.pl/_msdcs/dc/_tcp

 

_kerberos and _ldap I have here:

Forward Lookup Zones/ad.komplex.info.pl/_sites/komplex-info/_tcp

 

In "%systemroot%\System32\Config" I don't have "_ldap._tcp.Domain_Name"

 

Nslookup

 

> _ldap._tcp.dc._msdcs.ad.komplex.info.pl
Server: ad.komplex.info.pl
Address: 192.168.88.201

*** ad.komplex.info.pl can't find _ldap._tcp.dc._msdcs.ad.komplex.info.pl: Non-existent domain

 

 

5 Replies

    • piotr's avatar
      piotr
      Copper Contributor

      Configure your DNS server to use a static Internet Protocol (IP) address. - Yes, 192.168.88.201
      Create a forward lookup zone named after your Active Directory. - I have attach it.
      Enable your domain zone to allow dynamic updates. - I have attach it too.

      netdiag /fix - doesn't work. I have attach it.

       

      I used "dcdiag /fix" and here what I have:

      C:\Users\Administrator.SERVER2016AD.004>dcdiag /fix
      
      Directory Server Diagnosis
      
      Performing initial setup:
         Trying to find home server...
         Home Server = Server2016AD
         * Identified AD Forest.
         Done gathering initial info.
      
      Doing initial required tests
      
         Testing server: komplex-info\SERVER2016AD
            Starting test: Connectivity
               The host 76a7d524-7979-40d8-ba37-c21ef98d201b._msdcs.ad.komplex.info.pl could not be resolved to an IP
               address. Check the DNS server, DHCP, server name, etc.
               Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
               ......................... SERVER2016AD failed test Connectivity
      
      Doing primary tests
      
         Testing server: komplex-info\SERVER2016AD
            Skipping all tests, because server SERVER2016AD is not responding to directory service requests.
      
      
         Running partition tests on : ForestDnsZones
            Starting test: CheckSDRefDom
               ......................... ForestDnsZones passed test CheckSDRefDom
            Starting test: CrossRefValidation
               ......................... ForestDnsZones passed test CrossRefValidation
      
         Running partition tests on : DomainDnsZones
            Starting test: CheckSDRefDom
               ......................... DomainDnsZones passed test CheckSDRefDom
            Starting test: CrossRefValidation
               ......................... DomainDnsZones passed test CrossRefValidation
      
         Running partition tests on : Schema
            Starting test: CheckSDRefDom
               ......................... Schema passed test CheckSDRefDom
            Starting test: CrossRefValidation
               ......................... Schema passed test CrossRefValidation
      
         Running partition tests on : Configuration
            Starting test: CheckSDRefDom
               ......................... Configuration passed test CheckSDRefDom
            Starting test: CrossRefValidation
               ......................... Configuration passed test CrossRefValidation
      
         Running partition tests on : ad
            Starting test: CheckSDRefDom
               ......................... ad passed test CheckSDRefDom
            Starting test: CrossRefValidation
               ......................... ad passed test CrossRefValidation
      
         Running enterprise tests on : ad.komplex.info.pl
            Starting test: LocatorCheck
               ......................... ad.komplex.info.pl passed test LocatorCheck
            Starting test: Intersite
               ......................... ad.komplex.info.pl passed test Intersite

Resources