While you do not need to change your environment configuration to use IPv6 addresses, keep the following system best practices in mind when you implement IPv6 with DualStack networking across your platform:

• Use the Splunk-provided set of IPv6 addresses to review and adjust your system's firewall rules to allow IPv6.
• If you have a custom configuration, review the IP settings for your universal forwarders. If you are using IPv6 DualStack networking in your configuration, add connectUsingIpVersion = 6-only to the [general] stanza in [server.conf|server.conf] on the universal forwarder so that splunkd will attempt to connect to the IPv6 address. See Use IPv6 DualStack networking for more information.
• If your system uses an HTTP Event Collector (HEC) endpoint, note that the HEC network load balancer is converted to dual stack and has the same DNS name.
• Amazon does not support IPv6 for Firehose but they do support AWS private link. For best results, double-check your implementation with your Splunk Solutions engineer.
• For managing IPv6 for any networking customizations or third party products for your on premise configuration, reach out to your Splunk Solutions engineer.