Nslookup no longer working on IPv6
-
For some reason (without any configuration changes), nslookups to IPv6 addresses just started failing for me. I have an address from DHCP and I can traceroute from the router, so I assume that everything is working correctly from there.
The internal LAN interface is set to "Track Interface". This seems to be working as all of my internal LAN IPv6 devices are able to obtain IPv6 addresses (I presume via Comcast?).
The problem comes in when I try to do an nslookup on any IPv6 DNS name (ipv6.google.com). The DNS server is not responding. I've configure unbound and can use that via IPv4 but I'm not actually sure which server I'm using for lookups on IPv6.. The address I get is:
C:\Users\Ryan>nslookup Default Server: UnKnown Address: 2601:6:7780:581a:20d:b9ff:fe37:xxxxIs this address external from Comcast or internal to the router? IPv6 is all very new to me so I'm trying to learn as I go along.
nslookups from here return the following:
> google.com Server: UnKnown Address: 2601:6:7780:581a:20d:b9ff:fe37:324a *** UnKnown can't find google.com: No response from serverI also can't seem to ping out from the LAN. Does anyone have suggestions on basic troubleshooting steps? This was working fine with absolutely no configuration changes.
C:\Users\Ryan>ping 2001:4860:4860::8888 Pinging 2001:4860:4860::8888 with 32 bytes of data: PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. PING: transmit failed. General failure. Ping statistics for 2001:4860:4860::8888: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)Any suggestions would be appreciated!
-
Reboot both the modem and pfsense and lets see what happens then… (in that order)
-
Same result. I can't for the life of me figure out what broke. :-/
-
This sort of thing is why I dumped the native ipv6 on TWC and installed a HE tunnel instead. The ISPs are still flakey with IPV6.
-
So I actually narrowed it down to my wireless network. I'm running an Aruba IAP cluster.. Something there is dropping all of the IPv6 traffic (which is weird because this too was working recently). I can troubleshoot with them tomorrow.
Thanks!
-
This sort of thing is why I dumped the native ipv6 on TWC and installed a HE tunnel instead. The ISPs are still flakey with IPV6.
Exactly what I did - I tried playing with comcast IPv6.. Up, down, networks would change lan side all the time. HE tunnel is stable, my /64s from my /48 never change ;) I have no plans on going back to isp ipv6 any time soon.
-
HE tunnel is stable, my /64s from my /48 never change ;) I have no plans on going back to isp ipv6 any time soon.
+1. Examples of IPv6 "implementation" on some local ISPs:
- A huge xDSL provider: when you ask for IPv6, you get CGN IPv4 instead of your current shiny public IPv4 that has not changed for years, plus one (!!!) /64. No /60, /56 or anything like that possible. The /64s are dynamic and changing all the time. Awesome. ::)
- Major cable provider: testing only, using dual-stack lite, IPs changing all the time, a general yuck… ;D
- Small local WISP: Huh, what's IPv6? Oh, so you want a public /29 instead? But we are running short of IPv4s... ::) ::) ::) (They actually have the - deprecated - 6to4 available without even knowing.)
