You installed a new AD domain and the new (and first) DC has not registered its SRV records in DNS. Name a few possible causes.

• During the Dcpromo.exe process on the first domain controller for a child domain, that domain controller points to the Active Directory-integrated DNS server in the parent domain as a primary DNS server.
• The Allow dynamic updates setting on the parent Active Directory-integrated DNS server is set to Only Secure Updates.
• To resolve this issue:
  1. In the parent domain, start the DNS snap-in.
  2. Open the Forward Lookup zone, right-click your domain name, and then click Properties.
  3. On the General tab, make sure that Allow dynamic updates is set to Yes. By default, this is set to Only Secure Updates.
  4. Stop and then restart the DNS service. At a command prompt, type the following lines, pressing ENTER after each line:net stop dnsnet start dns
  5. On the child domain controller, stop and then restart the Netlogon service. This registers SRV records. At a command prompt, type the following lines, pressing ENTER after each line:
  6. net stop netlogon
  7. net start netlogon

Issue with Dynamic updates

 The DNS server is configured as a DHCP client. The DNS zone has a name other than your Active Directory domain name.   The zone is not enabled to allow dynamic updates and the local interface on the DNS server was not configured to allow dynamic updates.

During the Dcpromo.exe process on the first domain controller for a child domain, that domain controller points to the Active Directory-integrated DNS server in the parent domain as a primary DNS server. The Allow dynamic updates setting on the parent Active Directory-integrated DNS server is set to Only Secure Updates.

DNS service cannot be run.