Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Advertise DNS over IPv6 to Windows 8  (Read 11021 times)

Liinux

  • Newbie
  • *
  • Posts: 1
Advertise DNS over IPv6 to Windows 8
« on: December 03, 2012, 02:41:10 PM »

I cannot get Windows 8 to accept an advertised DNS server, no matter what I do.

A tested iPhone and a tested Windows 7 laptop works fine, and Windows 8 gets its IPv6 address and gateway correctly, just not the dns server.

My setup:
OpenBSD router on a dynamic IPv4 connection, running: rtadv, route6d and wide-dhcpv6.

rtadvd.conf
Code: [Select]
em1:\
        :addr="my-prefix":prefixlen#64:raflags#64:

dhcp6s.conf
Code: [Select]
option domain-name-servers my-prefix::1;
dhcp6s in debug mode gives the following output when addressing Windows 8's request.
Code: [Select]
Dec/03/2012 23:31:53: server6_recv: received solicit from <snip>
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option elapsed time, len 2
Dec/03/2012 23:31:53:   elapsed time: 3100
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option client ID, len 14
Dec/03/2012 23:31:53:   DUID: <snip>
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option identity association, len 12
Dec/03/2012 23:31:53:   IA_NA: ID=314355397, T1=0, T2=0
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option client FQDN, len 10
Dec/03/2012 23:31:53: dhcp6_get_options: unknown or unexpected DHCP6 option client FQDN, len 10
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option vendor class, len 14
Dec/03/2012 23:31:53: dhcp6_get_options: unknown or unexpected DHCP6 option vendor class, len 14
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option option request, len 8
Dec/03/2012 23:31:53:   requested option: domain search list
Dec/03/2012 23:31:53:   requested option: DNS
Dec/03/2012 23:31:53:   requested option: vendor specific info
Dec/03/2012 23:31:53:   requested option: client FQDN
Dec/03/2012 23:31:53: react_solicit: client ID <snip>
Dec/03/2012 23:31:53: copy_option: set client ID (len 14)
Dec/03/2012 23:31:53: copy_option: set server ID (len 14)
Dec/03/2012 23:31:53: copy_option: set status code (len 2)
Dec/03/2012 23:31:53: copy_option: set DNS (len 16)
Dec/03/2012 23:31:53: server6_send: transmit advertise to <snip>

As I said, other clients seems to work fine. Is this a Windows 8 bug, or a new default that I need to address?

Thanks in advance for your time!
Logged

wswartzendruber

  • Newbie
  • *
  • Posts: 33
Re: Advertise DNS over IPv6 to Windows 8
« Reply #1 on: March 16, 2013, 03:52:46 PM »

I can't get Windows 8 to take DNS via DHCPv6, either.  It was working fine on Windows 7.
Logged

aandaluz

  • Newbie
  • *
  • Posts: 18
Re: Advertise DNS over IPv6 to Windows 8
« Reply #2 on: May 18, 2013, 11:11:22 AM »

perhaps it's a bit too late to answer this question, but I've also experienced this issue and the only way to fix it was to reset the ipv6 interface using the netsh in an admin command prompt and the rebooting the machine:
netsh interface ipv6 reset
Logged

raida

  • Newbie
  • *
  • Posts: 1
Re: Advertise DNS over IPv6 to Windows 8
« Reply #3 on: September 26, 2013, 09:45:35 AM »

I cannot get Windows 8 to accept an advertised DNS server, no matter what I do.

A tested iPhone and a tested Windows 7 laptop works fine, and Windows 8 gets its IPv6 address and gateway correctly, just not the dns server.

My setup:
OpenBSD router on a dynamic IPv4 connection, running: rtadv, route6d and wide-dhcpv6.

rtadvd.conf
Code: [Select]
em1:\
        :addr="my-prefix":prefixlen#64:raflags#64:

dhcp6s.conf
Code: [Select]
option domain-name-servers my-prefix::1;
dhcp6s in debug mode gives the following output when addressing Windows 8's request.
Code: [Select]
Dec/03/2012 23:31:53: server6_recv: received solicit from <snip>
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option elapsed time, len 2
Dec/03/2012 23:31:53:   elapsed time: 3100
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option client ID, len 14
Dec/03/2012 23:31:53:   DUID: <snip>
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option identity association, len 12
Dec/03/2012 23:31:53:   IA_NA: ID=314355397, T1=0, T2=0
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option client FQDN, len 10
Dec/03/2012 23:31:53: dhcp6_get_options: unknown or unexpected DHCP6 option client FQDN, len 10
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option vendor class, len 14
Dec/03/2012 23:31:53: dhcp6_get_options: unknown or unexpected DHCP6 option vendor class, len 14
Dec/03/2012 23:31:53: dhcp6_get_options: get DHCP option option request, len 8
Dec/03/2012 23:31:53:   requested option: domain search list
Dec/03/2012 23:31:53:   requested option: DNS
Dec/03/2012 23:31:53:   requested option: vendor specific info
Dec/03/2012 23:31:53:   requested option: client FQDN
Dec/03/2012 23:31:53: react_solicit: client ID <snip>
Dec/03/2012 23:31:53: copy_option: set client ID (len 14)
Dec/03/2012 23:31:53: copy_option: set server ID (len 14)
Dec/03/2012 23:31:53: copy_option: set status code (len 2)
Dec/03/2012 23:31:53: copy_option: set DNS (len 16)
Dec/03/2012 23:31:53: server6_send: transmit advertise to <snip>

As I said, other clients seems to work fine. Is this a Windows 8 bug, or a new default that I need to address?

Thanks in advance for your time!
Logged