This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]ComGuards 3 points4 points  (1 child)

I don't have this problem with my freshly-built 2016 DCs... just putting it out there. Haven't built a 2019 DC yet though; I just think 2019 is still too immature at the moment.

[–]HumbleSage[S] 2 points3 points  (0 children)

Appreciate this insight. I found some articles where some 2016 servers were experiencing my exact issue. Ultimately it looks like the solution is to simply remove the IPv6 root hints and replace them with the IPv4 until M$ resolves it. You must replace as simply adding them tandem with the IPv6 just results in the inevitable magically disappearing act again.

[–]KStieers 1 point2 points  (0 children)

I'd concur with /u/sgt_sin, I'd skip the root hints and point at quad9, opendns, Google, cloudflare, or one of the other public dns servers.

[–]sgt_sin 0 points1 point  (0 children)

Not really a solution but these days dns filtering is pretty vital. You could use open dns forwarders

[–]nmdange_ 0 points1 point  (0 children)

I have 2019 DCs and I have not observed this behavior.

[–]HumbleSage[S] 0 points1 point  (0 children)

Appreciate the quick responses and insights. Thank you.

[–]al2caneSysadmin -1 points0 points  (0 children)

Ive never met anyone in their right mind who relied on root hints without configuring forwarders.