Deployment Architecture

In a clustered deployment, can you reference the master node by a DNS name instead of an IP?

kdoonan
Explorer

Eg, if you specify the master as master.domain.local? This may be a silly question but will it cause any issues? The idea being that if the master goes down, we can relaunch it and just change the DNS to point to the new server.

Some follow on questions:

If we do this and change the DNS, will the nodes resolve the change automatically?

If there are 2 master servers running, but only 1 of them is being sent data, will it cause any issues? Eg, if we do relaunch the server and then the original one recovers.

Thanks

Tags (2)
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

I see no reason not to use a DNS name. http://docs.splunk.com/Documentation/Splunk/6.1.2/Indexer/Handlemasternodefailure#Ensure_that_the_pe... explicitly mentions using DNS as well.

As for the old master coming back up, your nodes won't notice because you've changed the DNS entry.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

I see no reason not to use a DNS name. http://docs.splunk.com/Documentation/Splunk/6.1.2/Indexer/Handlemasternodefailure#Ensure_that_the_pe... explicitly mentions using DNS as well.

As for the old master coming back up, your nodes won't notice because you've changed the DNS entry.

Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...