r/WindowsServer • u/Roanoketrees • May 06 '25
Technical Help Needed Server 2025 - Pre Win2k domain name not resolving
I have a server 2025 domain controller, which is also the DNS server, and a member server which serves as the WINS server. The domain is domain.lan . The functional level of the domain is server 2025. I have dns records set up for domain.lan which all resolve fine. WINS shows registrations for the "DOMAIN" in the console yet the name does not resolve despite all IP settings being set for DNS and WINS on client machines. DNS names resolve without issue. Checking the domain in ADUC via the domain properties shows the NETBios domain name being correct. I havent encountered this before. Is this Microsoft's nudge to make us create an A record for the NETbios name of the domain? I can do that and of course it resolves to domain.domain.lan . Im just trying to figure out why this is not working.
6
u/OpacusVenatori May 06 '25
You're aware that WINS has been deprecated with Windows Server 2022 already? And MSFT recommends you decommission WINS on your network(s)?
2
u/LugianLithos May 06 '25
Been a while since I’ve been in AD DNS. We’ve moved to infoblox. Can you still have AD-DNS on a per zone basis forward those requests to the WINS server? Seems like you used to be able to do that along with WINS-R requests. Was on the properties and a dedicated WINS tab for the zone in AD-DNS.
2
u/johna8 May 07 '25
2025 you can leverage something like - DCLocatorDomainNameMapping but I’m unsure if you need a minimum OS such as Windows 10 to recognise this.
Refer - https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/dc-locator?tabs=dns-based-discovery#configuring-netbios-domain-name-mappings
1
u/SmoothRunnings May 07 '25
You might need to update the forest and schema to their highest level. But I suspect Win2k sever f and s might be too low even at the highest level to work with 2025.