Adding my 2p, I would take that principle a step further. Create a generic, unique SRV record that represents what you want to happen. Then create specific CNAME records for each server. The reasons for the extra, generic record are that it represents the service you want to offer and all "server.." records you want to use that service are identical in structure. e.g.
imap-tcp-service.example.com. SRV <priority weight port target> _imap._tcp.server1.example.com. CNAME imap-tcp-service.example.com. _imap._tcp.server2.example.com. CNAME imap-tcp-service.example.com. ... _imap._tcp.server999.example.com. CNAME imap-tcp-service.example.com. and so on. Cheers, Greg On Thu, 16 May 2024 at 11:43, Niall O'Reilly <niall.orei...@ucd.ie> wrote: > On 14 May 2024, at 15:20, DEMBLANS Mathieu wrote: > > A part of the subdomains are managed by us, others subdomains by an other > entity. > So we can't configure a generic target for all subdomains as each entity > has its own target for SRV entries. > > -----Message d'origine----- > > De : bind-users bind-users-boun...@lists.isc.org De la part de Matus > UHLAR - fantoms > Envoyé : mardi 14 mai 2024 15:58 > À : bind-users@lists.isc.org > Objet : Re: SRV on multiple subdomains > On 14.05.24 13:08, DEMBLANS Mathieu wrote: > > I have a question about configuration simplification for SRV configuration > (maybe it can be applyed for other entries). > > We manage multiple subdomain of a main one (server1.example.com, > server2.example.com,...). > For A and MX entries, we use a general domain definitions with wildcard > but is there a way to do so for SRV without having to define all subdomains > (we have several dizains of it) ? > > We have to define some SRV entries with the same target like : > _imap._tcp.server1.example.com IN SRV main.exemple.com > _imap._tcp.server2.example.com IN SRV main.exemple.com > > Since a record is needed for each host, I think I would use something like > this: > > imap._tcp.server1.example.com. IN SRV main.example.com. > imap._tcp.server2.example.com. IN CNAME imap._tcp.server1.example.com. > ... > imap._tcp.servern.example.com. IN CNAME imap._tcp.server1.example.com. > > The advantage here is that, if ever the target of the SRV record had to > be changed, only one record would have to be updated. > > /Niall > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
