SRV record specifies the hostname and port of a service within your domain — useful when a service lives on a non-standard port or needs load balancing across multiple servers. The format is _service._proto.name TTL class SRV priority weight port target.
Common uses: SIP/VoIP (port 5060), XMPP messaging, Kerberos authentication, email autodiscovery. You define priority (preferred server order) and weight (load distribution among equal-priority hosts).
Why it matters for bunkerdomains users: If you're running a privacy-focused communication platform, decentralized service, or offshore infrastructure, SRV records let you distribute traffic without exposing all backend details in A records. You can rotate servers, hide physical topology, and fail over gracefully—useful when jurisdiction or DDoS pressure demands it.
Related: MX records handle mail routing similarly; NS records point to nameservers. SRV is more specialized—think of it as the targeting layer for non-HTTP services. Requires proper TTL management; changes can take time to propagate.