dhcpinform request from Vista gets wrong Name servers

[Randall C Grimshaw]

Sorry to use the bandwidth, but for the benefit of those schools following this thread. these names may also be useful for some Vista versions.
6to4.ipv6.microsoft.com.                IN      A       192.88.99.1
time.windows.com.                       IN      A       207.46.130.100

<><Randy

________________________________

From: Randall C Grimshaw
Sent: Wed 8/15/2007 1:39 PM
To: Randall C Grimshaw; dhcp-users at isc.org
Subject: RE: dhcpinform request from Vista gets wrong Name servers


I will answer my own question. After defining teredo.ipv6.microsoft.com in the captive DNS server, Vista no longer requests Name servers in the option list of the followup dhcpinform packet, and works correctly with the captive DNS Name server.
 
; these are the vista dhcpinform solution
teredo.ipv6.microsoft.com.              IN      A       65.54.227.136
teredo.ipv6.microsoft.com.              IN      A       65.54.227.138
teredo.ipv6.microsoft.com.              IN      A       65.54.227.140
teredo.ipv6.microsoft.com.              IN      A       65.54.227.142
teredo.ipv6.microsoft.com.              IN      A       65.54.227.144
 
 <><Randy

________________________________

From: Randall C Grimshaw
Sent: Wed 8/15/2007 12:05 PM
To: dhcp-users at isc.org
Subject: dhcpinform request from Vista gets wrong Name servers


We run a network where dhcp gives unknown machines an address and configuration different by subnet from known machines.
DNS is one of these subnet based configurations that is given based on access to the pool granted by access permissions of known.
The DNS server for unknown systems resolves most addresses to a registration web server.
The Vista machines initially get the correct DNS settings and query for isatap (which resolves to the registration system) then queries for teredo.ipv6.microsoft.com (which resolves to the registration system).... then the rub... the Vista machine will perform a dhcpinfo query for name servers among other things and get the default name servers in the dhcpack - the default (production) name servers cannot be reached from the captive subnets and wouldn't direct users to the registration system if they were.
 
I am not sure if this is a bug in ISC dhcp by RFC or not.
Does snyone know if the dhcpinfo is a response to unexpected answer to the other two queries?
 
Thank you.
<><Randy