Microsoft Direct Access and Windows forwarder client, DNS, and IPv6 tunnels

[jtrucks]

Using the Windows forward client, is there a way to force the client to only use an IPv6 tunnel?

Situation: using Microsoft Direct Access (the new remote access solution)...
... the splunk forwarder client talks to deployment server...
... (via an IPv6 tunnel since to talk to the IPv4 only deployment server)...
... which then pushes an app that has the hostname of the forwarder, which only translates to IPv4...
...then the windows client forwarder bypasses the IPv6 tunnel and tries to talk to the IPv4 address of the destination forwarder server directly (which fails since it's not internet accessible).

Is there a way to configure the Windows client to use the IPv6 tunnel while Direct Access has the tunnel active?

[jtrucks · Accepted solution]

The answer is to enable IPv6 on the client. This is accomplished according to http://docs.splunk.com/Documentation/Splunk/5.0.2/Admin/ConfigureSplunkforIPv6 by editing:

$SPLUNK_HOME/etc/system/local/server.conf

to add:
[general]
listenOnIPv6=yes

Then restarting the client.

[halr9000]

Can you elaborate on "which only translates to IPv4"? Is that a part of a problem in DNS?