Bug in 15.1(3)T3 when trying to add an IPv6 name-server?

[andrew.butterworth]

I have an 877 that I have configured with IPv4 & IPv6 (via a tunnel broker).  I also VPN into this using VPDN with Windows 7 clients.  I have configured the VPN for IPv6 and this is working well.  Unfortunately an IPv6 name-server isn't being sent to the VPN client so I tried adding the IPv6 name servers to the 877 and it won't accept them.  I think this is a bug as I can add them on a Catalyst 3560 I have running 15.0(1)SE.

cisco-877(config)#ip name-server FEC0:0:0:FFFF::1

Not a valid name-server address - 254.192.0.0

Is this a known bug and is it fixed in any other releases?

Andy

[wzhang]

Hi,

I believe you are running into CSCti47529 (Reject "ip name-server" command when server have IPv6 ULA). Can you try 15.1(4)M or a later version?

Thanks,

Wen

[andrew.butterworth]

Hi Wen

I have put 15.1(4)M3 and this now accepts the IPv6 name servers.  This hasn't solved my issue however with the VPDN configuration.  I was hoping it would just automatically push the IPv6 DNS servers to the Windows client as there isn't the equivalent 'async-bootp dns-server' for IPv6?

Andy

[andrew.butterworth]

I managed to work around my issue by configuing both IPv6CP for address assignment to the client and DHCPv6 relay to supply DNS (and other) information.  See the IPV6 Dial Access thread - https://supportforums.cisco.com/thread/2127028?tstart=0

I am not sure this is the final configuration as it appears there is the possibility DNS will find its way into IPv6CP - http://tools.ietf.org/html/draft-huang-ipv6cp-options-00

Andy