Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Ipv6 Dns problem  (Read 8474 times)

Gorovoro

  • Newbie
  • *
  • Posts: 34
Ipv6 Dns problem
« on: November 02, 2013, 04:27:47 AM »

Hi,

I seem to be having a DNS problem.

Code: [Select]
Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-09
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8194:3f20:9963:5d0b%23(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.0.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, November 02, 2013 12:02:55 PM
   Lease Expires . . . . . . . . . . : Saturday, November 02, 2013 2:02:55 PM
   Default Gateway . . . . . . . . . : 10.0.0.138
   DHCP Server . . . . . . . . . . . : 10.0.0.138
   DNS Servers . . . . . . . . . . . : 10.0.0.138
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-09
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f14:1ef0::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::349c:1e48:f8d5:d41e%25(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:1f14:1ef0::1
   DNS Servers . . . . . . . . . . . : 10.0.0.138
   NetBIOS over Tcpip. . . . . . . . : Disabled


Code: [Select]
Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
Yes      Manual    256  ::/0                       25  2001:470:1f14:1ef0::1
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface
 1
No       Manual    256  2001:470:1f14:1ef0::/64    25  IP6Tunnel
No       Manual    256  2001:470:1f14:1ef0::2/128   25  IP6Tunnel
No       Manual    256  fe80::/64                  25  IP6Tunnel
No       Manual    256  fe80::/64                  16  Tunngle
No       Manual    256  fe80::/64                  23  Local Area Connection 2
No       Manual    256  fe80::5efe:10.0.0.1/128    12  isatap.Home
No       Manual    256  fe80::349c:1e48:f8d5:d41e/128   25  IP6Tunnel
No       Manual    256  fe80::8194:3f20:9963:5d0b/128   23  Local Area Connectio
n 2
No       Manual    256  fe80::a5ec:1dcf:882:e4af/128   16  Tunngle
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface
 1
No       Manual    256  ff00::/8                   25  IP6Tunnel
No       Manual    256  ff00::/8                   16  Tunngle
No       Manual    256  ff00::/8                   23  Local Area Connection 2

I can't ping or lookpup any ipv6, help would be appreciated.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: Ipv6 Dns problem
« Reply #1 on: November 02, 2013, 06:18:32 AM »

So what you're saying is you have a tunnel issue? I'm going to guess you can't even ping the he side of your tunnel?
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #2 on: November 02, 2013, 06:27:06 AM »

you mean like this?

Code: [Select]
D:\Users\Admin>ping 216.66.84.46

Pinging 216.66.84.46 with 32 bytes of data:
Reply from 216.66.84.46: bytes=32 time=78ms TTL=52
Reply from 216.66.84.46: bytes=32 time=77ms TTL=52
Reply from 216.66.84.46: bytes=32 time=79ms TTL=52
Reply from 216.66.84.46: bytes=32 time=77ms TTL=52

Ping statistics for 216.66.84.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 79ms, Average = 77ms

D:\Users\Admin>ping -6 2001:470:1f14:1ef0::1

Pinging 2001:470:1f14:1ef0::1 with 32 bytes of data:
Reply from 2001:470:1f14:1ef0::1: time=77ms
Reply from 2001:470:1f14:1ef0::1: time=78ms
Reply from 2001:470:1f14:1ef0::1: time=78ms
Reply from 2001:470:1f14:1ef0::1: time=78ms

Ping statistics for 2001:470:1f14:1ef0::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 78ms, Average = 77ms
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: Ipv6 Dns problem
« Reply #3 on: November 02, 2013, 07:29:06 AM »

He means the HE IPv6 address of the tunnel. When you ran the Windows commands to bring up the tunnel, did you use 10.0.0.2?

-Edit- my bad, didn't see your code window had a scrollbar.
« Last Edit: November 02, 2013, 08:23:42 AM by broquea »
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #4 on: November 02, 2013, 07:39:48 AM »

I use my own script which i've created using several guides etc.

Code: [Select]

netsh interface ipv6 reset
netsh interface ipv6 del address IP6Tunnel 2001:470:1f14:1ef0::2
netsh interface ipv6 del route ::/0 IP6Tunnel 2001:470:1f14:1ef0::1
netsh interface ipv6 delete interface IP6Tunnel
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 10.0.0.2 216.66.84.46
netsh interface ipv6 add address IP6Tunnel 2001:470:1f14:1ef0::2
netsh interface ipv6 set interface IP6Tunnel forwarding=enabled
netsh interface ipv6 set interface "Local Area Connection 2" forwarding=enabled advertise=enabled
netsh interface ipv6 add addr "Local Area Connection 2" 2001:470:1f15:1ef0::1
netsh interface ipv6 add route 2001:470:1f15:1ef0::/64 "Local Area Connection 2" publish=yes
netsh interface ipv6 add route ::/0 "IP6Tunnel" 2001:470:1f14:1ef0::1 publish=yes
pause
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: Ipv6 Dns problem
« Reply #5 on: November 02, 2013, 08:25:44 AM »

What happens when you query 8.8.8.8 or 8.8.4.4 or 2001:470:20::2 or 74.82.42.42 for AAAA records of hosts like ipv6.google.com?

And what happens when you query 10.0.0.138 for the same record? I Ask because that appears to be your only listed DNS server for queries.
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #6 on: November 02, 2013, 12:51:56 PM »

It seems that only 10.0.0.138 which is my router doesn't answer, also i have the static dns servers in my router set to google that is 8.8.8.8 and 8.8.4.4 so this doesn't make sense to me.

Code: [Select]
D:\Users\Admin>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  10.0.0.138

> server 10.0.0.138
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [10.0.0.138]
Address:  10.0.0.138

> ipv6.google.com
Server:  [10.0.0.138]
Address:  10.0.0.138

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [10.0.0.138] timed-out

> server 8.8.8.8
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [8.8.8.8]
Address:  8.8.8.8

> ipv6.google.com
Server:  [8.8.8.8]
Address:  8.8.8.8

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2a00:1450:4017:800::1011
Aliases:  ipv6.google.com

> server 8.8.4.4
Default Server:  google-public-dns-b.google.com
Address:  8.8.4.4

> ipv6.google.com
Server:  google-public-dns-b.google.com
Address:  8.8.4.4

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2a00:1450:4017:800::1011
Aliases:  ipv6.google.com

> server 74.82.42.42
Default Server:  ordns.he.net
Address:  74.82.42.42

> ipv6.google.com
Server:  ordns.he.net
Address:  74.82.42.42

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2a00:1450:4001:800::1012
Aliases:  ipv6.google.com

> server 2001:470:20::2
Default Server:  ordns.he.net
Address:  2001:470:20::2

> ipv6.google.com
Server:  ordns.he.net
Address:  2001:470:20::2

Non-authoritative answer:
Name:    ipv6.l.google.com
Address:  2a00:1450:4013:c01::69
Aliases:  ipv6.google.com

Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: Ipv6 Dns problem
« Reply #7 on: November 02, 2013, 05:30:35 PM »

What is 10.0.0.138? Some sort of NAT appliance? There have been some make/models out there that are weird and don't return AAAA replies. You could try having it hand out the Google DNS IPs instead of itself.
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #8 on: November 03, 2013, 11:05:22 AM »

10.0.0.138 is my router it's a dlink router that until recently worked just fine with my tunnel for the last 3 years
How do i set it to hand out google?
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #9 on: November 03, 2013, 01:41:12 PM »

Ok last update
it looks like my router has gone insane for some reason and choose to ignore the DNS i gave him or something, trying to set it manually again or importing old configuration changed it back but it's as if nothing has changed meaning it still didn't work.

so finally i choose to set it on the windows side i.e. in the tcp\ip connection settings in my connection and it instantly fixed all issues.

Thanks for all you help.
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: Ipv6 Dns problem
« Reply #10 on: November 03, 2013, 04:50:26 PM »

Has the Dlink been rebooted at all? I don't just mean the services, but actually rebooted/powercycled. Maybe some sort of failure that needs it cycled.
Logged

Gorovoro

  • Newbie
  • *
  • Posts: 34
Re: Ipv6 Dns problem
« Reply #11 on: November 04, 2013, 11:22:35 AM »

Of course i tried rebooting i also tried factory reset, restoring backup settings and more. but it still didn't work for some reason.
Logged