Reputation
1,750
Next privilege 2,000 Rep.
Edit questions and answers
Badges
6 8
Newest
 Yearling
Impact
~117k people reached

Jun
24
awarded  Yearling
Sep
24
awarded  Autobiographer
Jun
24
awarded  Yearling
Jun
24
awarded  Yearling
Jan
17
answered Windows DNS answers NXDOMAIN for local zone from VPN
Jan
17
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas At least you have been able to identify the source of the problem, maybe there's a way to turn that feature off on the VPN or reconfigure it to forward the DNS queries properly. Either way, good luck.
Jan
16
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas Sorry then, outside of any crazy permissions, I'm completely out of ideas. If the only goal is to get this workstation on the domain, then you could of course fake it all by adding the appropriate entries into the HOSTS file. That's a major hack, but if it gets you where you need to be then I would go ahead and do it.
Jan
16
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas Is it possible that the VPN is intercepting/modifying the DNS queries? Can you do the same query on the local network and have it return the proper results?
Jan
16
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas Can you make that query and get a result?
Jan
15
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas I think that's your problem, I think your client is actually querying the wrong servers (which is very common with VPNs). Just as an experiment, remove the primary/secondary DNS settings from your internet connection (after the VPN is connected obviously) and then try to join the domain and see what happens.
Jan
15
comment Windows DNS answers NXDOMAIN for local zone from VPN
@Thomas BTW, FWIW, when you're adding a workstation to a domain, it's actually going to query for something like gc._msds.company.local. So you might be chasing the wrong rabbit.
Jan
15
comment Windows DNS answers NXDOMAIN for local zone from VPN
I'm not sure if this is just because you were trying to obfuscate some of the names or not, but I notice the server is xyz.cloud.internal, but you are querying for company.local. Is this server authoritative for company.local?
Jan
15
comment Windows DNS answers NXDOMAIN for local zone from VPN
If you do the same nslookup from a client that is on the same subnet, does it respond as you would expect?
Jan
15
comment DNS Server resolves external address,when vpn dns should resolve internal address
I think this is a side-effect of (what is IMHO a bad practice) using "split DNS" where the DNS names resolve differently based on what DNS server you're querying. Assuming you can get the DNS client to query the proper DNS server, you're still going to run a problem with caching. Assuming the client resolves the IP from the public internet, it will cache that result, and then when you connect the VPN chances are good it will not attempt to re-query, it will simply use the cached result.
Jan
15
awarded  Enlightened
Jan
15
awarded  Nice Answer
Jun
25
comment Too many concurrent connections Exchange 2010. What else is there to check?
How is "the email client" sending the mail. Is it just opening 1 connection per recipient without any limits? Also, after you start getting this error message, can the mass mailer continue and retry to send the messages after the errors?
Jun
25
comment Too many concurrent connections Exchange 2010. What else is there to check?
What Exchange role is the server in question?
Jun
24
awarded  Yearling
Mar
26
comment Users getting 'flooded' with not read notifications (NRNs) for old emails and meeting requests
It seems that your problem is exactly matching the one fixed by this update, so it seems reasonable that after 120 days your problem will go away. But I can't confirm for sure that it will.