Score:0

Workstations on a Windows Network have strange FQDNs in DNS

my flag

I manage a site with around 50 Windows desktop PCs.

On the network is a single domain controller, file server and deployment server all running Windows Server 2022 (up to date).

Recently, I've noticed a number of PCs with strange FQDNs: DHCP list of clients with hedani.net FQDNs

There is no entry for that domain in DNS, however running nslookup on the DC returns: NSLookup of Hedani.net from the DC

Here is a list of things I've tried:

  • All PCs on-site have recently been rebuilt and only have Office and Sophos AV installed.
  • Antivirus has found no malware
  • Cleared DNS cache
  • Checked DNS config on both the servers and affected clients
  • Hostname is correct on the affected clients
  • Windows is up to date site-wide
  • Deleting the DHCP entry and renewing the IP of the machine does fix the strange FQDN to the networks internal address, however this is a temporary fix.
bjoster avatar
cn flag
Do the clients use any VPN oder are there multiple WLANs? Looks like some clients took a local domain and tried registering them with you (and were successful).
joeqwerty avatar
cv flag
What DNS Domain Name are you assigning the DHCP clients from your DHCP scope or server options?
felpsey avatar
my flag
Clients do not use VPN on desktop machines (which are the ones affected), there aren't multiple WLANS. The DNS Domain Name assigned is OrgName.Internal.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.