D
Dennis Leiterman
Hi,
I have been trying to figure this one out and
I was hoping that someone might be able to help.
Here is the setup;
Windows 2000 with the primary dns suffix
set to a.com and then having the connection
specific domain suffix set to b.com via dhcp.
In the b.com domain I have wpad pointing to
our IIS server with wpad.dat located in the
web root directory. I have read that IE should
do the following lookups;
wpad.a.com, then wpad.b.com. When looking at
it with Network Monitor, I just see the
wpad.a.com. If I bring up a command window and
I try to ping wpad by itself, I see both queries.
I have flushed my dns cache on the system and it
still only tries to resolve the primary dns suffix
domain and not the connection specific domain.
This has happened with IE5 and IE6 with the
lastest service packs. If I put b.com as the
primary dns suffix, it works fine.
Thanks in advance!!!
I have been trying to figure this one out and
I was hoping that someone might be able to help.
Here is the setup;
Windows 2000 with the primary dns suffix
set to a.com and then having the connection
specific domain suffix set to b.com via dhcp.
In the b.com domain I have wpad pointing to
our IIS server with wpad.dat located in the
web root directory. I have read that IE should
do the following lookups;
wpad.a.com, then wpad.b.com. When looking at
it with Network Monitor, I just see the
wpad.a.com. If I bring up a command window and
I try to ping wpad by itself, I see both queries.
I have flushed my dns cache on the system and it
still only tries to resolve the primary dns suffix
domain and not the connection specific domain.
This has happened with IE5 and IE6 with the
lastest service packs. If I put b.com as the
primary dns suffix, it works fine.
Thanks in advance!!!