Vista keeps name server options from previous lease

Frank Sweetser fs at WPI.EDU
Sat Sep 15 18:22:42 UTC 2007

Randall C Grimshaw wrote:

> There is a workaround that works much of the time but not all. Vista always
> does a dhcpinform request but does not always include the nameserver option
> in the request. It seems that the trigger for including the nameserver
> option is a failure to resolve IPv6 tunnel coordination server names. The
> workaround is to define the servers in your captive DNS. It may not always
> be required that they are reachable. As an aside, I was not amuzed to look
> up how destructive a teredo is.

A lot of places (including here) are having these problems in a
pre-registration or quarantine configuration, where even if Vista were capable
of resolving those addresses, any traffic to or from them would be blocked.
Do you know if merely getting an answer back for those records is adequate,
such as one returned via a wildcard record, or will the problem still occur if
the client gets an answer, but can't setup a tunnel with whatever address the
query returns?

Frank Sweetser fs at  |  For every problem, there is a solution that
WPI Senior Network Engineer   |  is simple, elegant, and wrong. - HL Mencken
    GPG fingerprint = 6174 1257 129E 0D21 D8D4  E8A3 8E39 29E3 E2E8 8CEC

More information about the dhcp-users mailing list