Outlook uses wrong DNS server when IPSec is active

[Guest]

I have an IPSec connection (over WLAN) running to my company network.
nslookup is correctly connecting to the company DNS server.
Outlook however contacts the DNS server of the WLAN connection (as can be
seen in a Wireshark snoop). Unfortunately it gets an answer and tries to make
its DCERPC connection to the address from this response (and fails).

Does anybody know why Outlook uses a different DNS server than nslookup, and
how this can be prevented or configured?

Versions: Windows XP SP2, Outlook 2002 SP3

 

[smlunatick]

I have an IPSec connection (over WLAN) running to my company network.
nslookup is correctly connecting to the company DNS server.
Outlook however contacts the DNS server of the WLAN connection (as can be
seen in a Wireshark snoop). Unfortunately it gets an answer and tries to make
its DCERPC connection to the address from this response (and fails).

Does anybody know why Outlook uses a different DNS server than nslookup, and
how this can be prevented or configured?

Versions: Windows XP SP2, Outlook 2002 SP3

You wish to use the DNS server(s) provided to your company's network?
You need to check to see if the IPSec connection (VPN) client can
force your PC to use the "default gateway" on the remote (company's)
network.

 

[Guest]

As mentioned, I already reached a point where e.g. nslookup DOES connect to
the correct (company) DNS server. I did this by editing
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind and bringing
Deice\NdisWanIp to the top.
The strange thing is that Outlook still uses the wrong (local) DNS server.

Th.