Help & Troubleshooting
SRV Record
What this is
SRV records advertise the host and port for a specific service and protocol, using a structured name like _sip._tcp.example.com. Only applications designed to look them up (VoIP, XMPP, some Microsoft services) use them.
How to read your result
Each result names priority, weight, port, and target host. Absence is only a problem if some application specifically requires the record — check that application's documentation for the exact _service._proto name it expects.
Common problems and how to fix them
SRV published under the wrong name
How it shows up: The application ignores the record entirely; autodiscovery keeps failing.
How to fix it: The name must match exactly what the application queries — including the underscores and the protocol label (_tcp vs _udp). Copy the exact name from the vendor's setup guide.
SRV target is a CNAME or lacks an address record
How it shows up: Some clients connect, others fail — strict implementations refuse CNAME targets.
How to fix it: Point the SRV target at a hostname that has its own A/AAAA record.