locked
DNS64 on one NLB Member not responding to requests RRS feed

  • Question

  • Hi.

    Just having a little issue with a 2-node NLB load-balanced DA with UAG 2010 SP1 deployment.  My two nodes are UAG1 and UAG2.  In the Web Monitor both nodes display as healthy for all services.  I am able to connect via DA and all is well. 

    However, if I stop UAG2 via the Web Monitor, I am unable to connect to resources by name.  I can however ping resources by IPv6 address.  So, it appeas that the tunnels are still up, but DNS64 is not responding.

    I have run Process Monitor on both UAG1 and UAG2 whilst using NSLOOKUP with the IPv6 address of the second of my two consecutive IP addresses from a DA-connected client.  On UAG1 I can see the 'dns_service.exe' service responding to the requests.  If I stop UAG1 and run the same on UAG2 there is no activity.

    I first thought this was an ARP issue, but it doesnt appear to be since general DA connectivity is up - just name resolution doesn't work. 

    Just wondering if anyone has had a similar issue?

    Cheers

    Shaun

    Thursday, November 24, 2011 3:57 PM

All replies