SRV-Record
Service-location record — specifies host AND port for a named service.
Was ist ein SRV-Record?
SRV (RFC 2782) lets clients discover where a named service lives without hard-coding a hostname or port. It encodes priority, weight, port, and target host. Used heavily by XMPP, Microsoft Active Directory, SIP, Matrix, Minecraft and many VoIP / federated services.
Beispiel-Zonendatei-Eintrag
_xmpp-client._tcp.example.com. 300 IN SRV 10 60 5222 xmpp1.example.com.
Typische Anwendungsfälle
- ▸XMPP / Jabber federation — _xmpp-client._tcp.
- ▸Active Directory service location — _ldap._tcp, _kerberos._tcp.
- ▸SIP / Matrix federation — _sip._tls, _matrix._tcp.
- ▸Minecraft non-standard server port — _minecraft._tcp.
Häufige Stolpersteine
Many client libraries only honour SRV for specific protocols; HTTP/HTTPS infamously do NOT use SRV (despite RFC drafts). For HTTP, use CNAME / A.