Looks like DNS is not started or AD is yet to complete its initial sync.
Cheers !
Shaba
Make sure the server is pointing to itself in the NIC config for primary DNS server. If there's another DNS server there, you can put that one in as the secondary.
OK - I need a clarification on the message. Does it occur on a continuing basis while the server is running? Or does it occur only when you reboot. That error is normal if it occurs only when you reboot, especially on a stand-alone DC (no other DCs on the network). It's part of the process that the AD services don't start up first, so when you reboot, you'll see that error but it's transient and doesn't affect the availability of AD services after the reboot is finished and all services are started.
In that case, you're fine - nothing to worry about. DNS is just complaining because the AD services aren't started yet, but it resolves itself later in the startup process. You'll continue to see this event any time you restart the server, but if you see it at any other time, then you need to investigate because it indicates that there's a problem with Active Directory on this server.
Did you authorize the DHCP server and set up a scope? Usually the error 1049 and 1046 are caused by having the DHCP service role installed but not configured.
The 10200 error is normal if you're not actively using IPv6 and haven't configured it with a static IP address. If you're not using it, there's no reason to configure it and you can just ignore the error.
Yes default lease time is fine especially in a test environment. Try restarting the DHCP server service. Sometimes you need to do that after authorization.
When you look at it in the DHCP console, does it show as authorized (green checkmark on IPv4 and IPv6)? Does the error reoccur on a regular basis or show only during restart?
Can you open the DNS console and check DNS settings? Check your DNS records for your DNS servers in a console and check DNS settings on the NIC.