Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"

Anything having to be done to the OS besides installing it out of the box for this feature to work properly is a "hack". No bandaids - even adding an IPv6 address should be required for this to work. It isn't in Server 2022. This should just work out of the box. By the way, in testing, demoting the server back to a member server returns the network adapter operation to normal. That's why I am convinced this has something to do with them removing the dependency on NLA, however, keeping the requirement as part of AD for some reason when the server becomes a DC. Guessing something wasn't coded properly. I hope to hear back from MS at some point on this.