none
IPV6 DNS resolution and Ping connectivity on DA Server RRS feed

  • Question

  • I have a Direct Access issue that is making me pull my hair out.

    The UAG server is unable to resolve any IPv6 DNS servers or ping any other hosts via ipv6 on the internal network. 

    All other computers in the same network can ping and resolve ipv6 names in the internal network. 

     

    DA server has IPV6 address of
    xxxx:xxx:xxxx::1

    DC which is hosting the DNS is
    xxxx:xxx:xxxx::2 

    I have given myself the IP of
    xxxx:xxx:xxxx::5

     

    From My machine to the DC ping works just fine, so does nslookup.

    From the DC to my machine ping works fine, so does nslookup.

    From DC to DA server we get

    Pinging xxxx:xxx:xxxx::1 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure. 

    From My machine to the DA server:

    Pinging xxxx:xxx:xxxx::1 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure.   

    From DA to DC

    Pinging xxxx:xxx:xxxx::2 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure. 

    From DA to me:

    Pinging xxxx:xxx:xxxx::5 with 32 bytes of data:
    General failure.
    General failure.
    General failure.
    General failure. 


    What could cause IPv6 to fail like this on only one box? This is the only box we have any issues with as far as IPv6 connectivity and resolution goes. 

     

    Any help is much appreciated!

    Tuesday, January 10, 2012 10:39 PM

All replies

  • General failure means this is a routing issue and not a DNS resolution issue.

    You can see DNS resolution works by trying to use nslookup.

    Since the UAG DA server is an edge server, it should have a slightly different routing configuration:

    • Default IPv6 route should be on an external interface (you can use 'netsh int 6to4 set relay 192.88.99.1' to create this route)
    • Routes for the organization IPv6 prefix should be configured on the internal IPv6 interface, with the closest IPv6 router configured as a next hop gateway.

    This is covered in the prerequisites article in TechNet (check routing prerequisite):

    http://technet.microsoft.com/en-us/library/dd857262.aspx

    Anyway, when you configure and activate UAG DA it warns you about any missing routes on the internal interface

    Wednesday, January 11, 2012 9:23 AM