[Vpn-help] 1.1.0 observation (bug? Maybe)

Peter Eisch peter at boku.net
Fri Oct 6 13:38:22 CDT 2006

On 10/6/06 11:52 AM, "Matthew Grooms" <mgrooms at shrew.net> wrote:

> I wanted to offer another case where it may be valid to see traffic
> being posed to the local DNS server. Looking at your previous ipconfig
> output, windows may be appending 'etude.com' to the DNS question in an
> attempt to resolve host names that may not be fully qualified. There are
> a lot of options for appending DNS suffixes in windows and I can't
> recall every test I ran in every scenario. If nothing else, the packet
> captures should give us more definitive evidence to work with.

["traces galore" sent]

If this case existed, the traces of the DNS requests would reflect that
domain in the query.  This isn't the case.  I've logged into the client with
a domain login and the system first attempts to register (single-sign-on)
with the domain controller whenever an interface comes up.  (as well as
other times)

I'd probably accept the appending of any available domainname -- so long as
the requests went to the right nameserver.

Maybe I should play with split networks and perhaps this goes away.  (I have
a problem with roadwarriors thinking they're protected when they're live on
the net in some hotel.  They do get some protection once the VPN is back up
to the office.  Thus I cringe at the split network configs.)


More information about the vpn-help mailing list