Dns not updating from dhcp 2016


Update: Microsoft employee John Wink revealed that the issue was caused by a service crash that broke DHCP. The correct mitigation was/is a restart (not shutdown/reboot, but start - power - restart).

(The link between BT and Plusnet is that, while the latter bills itself as a friendly independent ISP, it's really a subsidiary of the former.) BT and Plusnet told The Register Microsoft is investigating the blunder.

I had to manually change the local IPv4 IP address for the network adapter to fix the issue.

Uninstalling KB3201845 should have the same effect but I have not tried that yet.

I am not sure what I did wrong but have attached the DHCP server portion of my config.

Time to re-hash why DNS is important, or actually, NEEDED for Active Directory, and Azure AD . ” He just stares at you not knowing what you’re talking about.

The same thing is occurring when you use an outside DNS server in your NIC properties (whether on the DC, member servers and/or client machines).

If the machines are set to use an outside DNS address, then your machines are literally asking an outside entity, “What’s the IP address of my domain controller? What will happen if you use an ISP’s DNS address, or a router as a DNS address on a DC or client machine, is the machine (whether a DC or client), will ask the ISP’s DNS, “What is my DC’s IP address?

It’s like me asking that guy down the street that I’ve never met, “Hey you, where did all the beer or milk go in my refrigerator? 🙂 I’ve read and responded to numerous newsgroup and forums posts requesting assistance, as well as new customers I’ve been called upon to fix issues, with such complaints as taking a long time to login, can’t access printers or mapped drives, Outlook fails to find the Exchange servers, among other issues.

After windows update and restart, my dhcp won't serve any new IP addresses.

The settings hasn't been changed, but I checked and it has a lot's of free IP -s and the scope is activated and the server is Authorized to serve DHCP.

Have you tried stopping and restarting the DHCP service on the server?

You must have an account to comment. Please register or login here!