Question

Locked

DNS issue when using VPN

By CraftyByte ·
There is a domain on the internet corp.com (not owned by us) which has an entry in its dns-records with a wildcard (*.corp.com)

Our AD domain is corp.com

The problem only occurs when using a VPN connection. Connecting to a resource on a domain other than corp.com fails. It first searches the primary DNS suffix, but does not find the resource here. Instead of searching in the DNS suffix search list (where it can be found), it searches a public DNS server and finds *.corp.com...

The DNS-suffixes are connection-specific suffixes for the VPN connection.

Why does the public DNS-server has priority over the DNS suffix search list defined in the connection?
Can anyone point me in the right direction to solve this problem?

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

AD

by Mehul Bhai In reply to DNS issue when using VPN

According to as much I know your local Active Directory Domain should be named XYZ.local where XYZ can be your company name in short or anything you wish and not XYZ.com unless until, ofcourse, if you have a registered Internet domain name of the type .com, .org, .gov, etc. owned ny your company and you want to use both in conjunction.

Back to Networks Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums