Issue #3669 has been updated by eric sorenson.
Since this is the original bug for SRV record support, I'll note here that _contra_ Josh's comments 26 and 27, srv record lookup is *disabled by default* in 3.0. It's true that this makes it not-zero-config, but there are a raft of issues including substantial slowdowns if the records are not available. https://github.com/puppetlabs/puppet/commit/ac1b9d55a95f27a54ff924081d68687792dbd194 ---------------------------------------- Feature #3669: Make puppet honor DNS SRV records https://projects.puppetlabs.com/issues/3669#change-71190 Author: Martin Marcher Status: Closed Priority: Normal Assignee: Category: Target version: 3.0.0 Affected Puppet version: development Keywords: Branch: https://github.com/jhelwig/puppet/tree/ticket/master/3669-make-puppet-honor-DNS-SRV-records I'd like to be able to define where puppet looks for the master server. I propose the following: By default try in the following order: 1. Look for a "_x-puppet._tcp.example.com" SRV record (or any name that you think is appropriate, but keep it a SRV record) 2. For backwards compatibility, if no SRV record is present look for puppet.example.com as a fallback or any value that is configured in the puppet config file Reasoning: A System Administrator can easily spread out the load over multiple puppet servers in this way or define some split horizon which answers with the "correct" hostname to use as a puppet master. Thanks, Martin -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
