- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![the_wolverine the_wolverine](https://community.splunk.com/legacyfs/online/avatars/55.jpg)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![the_wolverine the_wolverine](https://community.splunk.com/legacyfs/online/avatars/55.jpg)
Looks like there is a document for this topic: http://docs.splunk.com/Documentation/Splunk/4.3.2/Deploy/Setuploadbalancingd#Targets_for_load_balanc...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![the_wolverine the_wolverine](https://community.splunk.com/legacyfs/online/avatars/55.jpg)
Looks like there is a document for this topic: http://docs.splunk.com/Documentation/Splunk/4.3.2/Deploy/Setuploadbalancingd#Targets_for_load_balanc...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DNS roundrobin, for deployment servers, indexers, or search heads?
Doesn't work quite right for Deployment Servers (yet) that we've tried, indexers should NOT be put into this configuration since it handles it using autolb. Search Pools are safe with search heads, but not independently since authentication becomes an issue.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![the_wolverine the_wolverine](https://community.splunk.com/legacyfs/online/avatars/55.jpg)
For indexers - e.g. configure a DNS zone file that will roundrobin to indexers so that we could configure a single server in the outputs.conf on a forwarder.
![](/skins/images/89D5ADE867CBAF0B5A525B7E23D83D7E/responsive_peak/images/icon_anonymous_message.png)