This is an automated archive.
The original was posted on /r/sysadmin by /u/BookkeeperOptimal246 on 2024-01-23 01:47:29+00:00.
Hey Guys and Gals,
I have an odd issue with a client of ours that started when we could not join machines to the domain over the VPN. Initially we thought the engineer pointed the machine at the wrong dns but we have the correct dns server and able to access it, the problem lies in the dns itself I believe.
Their current domain name is Widget but not widget.local or .com like a normal domain in the dns manager. When we do a nslookup from a machine in their local network it comes back as widget.widget and pointing at their DC ip address.
When we attempt the same on the other side it comes back as unknown with the ip of their local DC, we inherited this client without any historical info so not quite sure how it got to this point.
Any ideas what we should do to correct this or transition them to a proper fqdn domain?