Error: 0x8007232B DNS name does not exist about py-kms HOT 4 CLOSED

Hi Matt!

Thank you very much for a prompt reply! Here is the unedited output (I guess I don't have anything to hide here):

PS C:\Users\admin> nslookup -type=srv _vlmcs._tcp
Server:  pi.hole
Address:  10.0.0.222

_vlmcs._tcp     SRV service location:
          priority       = 20
          weight         = 0
          port           = 1688
          svr hostname   = kms.example.com
kms.example.com     internet address = 10.0.0.227
PS C:\Users\admin> Test-NetConnection kms.example.com -Port 1688


ComputerName     : kms.example.com
RemoteAddress    : 10.0.0.227
RemotePort       : 1688
InterfaceAlias   : Ethernet 2
SourceAddress    : 10.0.0.20
TcpTestSucceeded : True

The copy of Windows that I'm trying to activate is not a new installation, it was installed from an official Microsoft ISO, none of the DLLs were replaced to third party versions, it was previously activated with a different key (not GVLK), but I have reset the activation with slmgr /upk. Also, when manually specifying the server with slmgr /skms kms.example.com:1688, the activation is successful. I think you are right about the reason for this behavior being connected with DNS search domain suffix and AD, I will look more into this.

from py-kms.

Hey,

good that @Matthew-Beckett already explained this (:heart:). I think Microsoft should update their docs to state in big, fat, red letters that using the SRV entry in DNS does only work in AD environments. I think this should solve your problem.

One final note Please refrain from using publicly accessible hostnames (like lahtihosting.fi) as Microsoft will scan those and send you a nice DMCA for providing this service.

Greetings...

from py-kms.

Hi @tpimh,

This is something which has come up in the past, please can you provide outputs with generalised host names as opposed to redacted as it makes it impossible to tell if your DNS solution is working as it should be.

Also, it may be helpful to refer to this thread where this issue has come up in the past, it may be full of useful information which may help you on your quest.

I would specifically read into the parts around DNS search domain suffix appending behaviours of the DNS Client in Windows and how that does (or seemingly doesn't) behave properly with the KMS Client, and also how it seems to depend on AD somehow.

Previous DNS Discovery Issue Thread: #45

Thanks,
Matt

from py-kms.

Hi Simon! I have no plans of providing such service, the subdomain only exists in a private network. All my copies of Windows are legit, and I'm using py-kms strictly for research purposes, so I really do think I'm not breaking any rules or laws. However, I have edited my messages and deleted the edit history (didn't know it was a feature).

from py-kms.