What this check shows
SRV records publish the hostname and port used by a named service. They are used by systems such as SIP, XMPP, Kerberos, LDAP and Microsoft services.
DNSRadar compares priority, weight, port and target values so service discovery changes can be checked across recursive caches.
When to use it
- VoIP and SIP configuration
- Microsoft 365 or Active Directory diagnostics
- Service discovery migrations
- Checking priority and weight changes
How to read the result
- Lower priority values are selected first; weight distributes traffic between records with the same priority.
- The target hostname must resolve separately and the advertised port must accept the service.
- Query the complete _service._protocol hostname rather than the bare domain.
Command examples
Use these dig commands when you need to compare DNSRadar with a terminal check or collect evidence for a DNS provider.
Terminal
dig _sip._tcp.example.com SRV +short
dig @1.1.1.1 _sip._tcp.example.com SRV
dig _xmpp-server._tcp.example.com SRV +noall +answerQuestions
What is the difference between priority and weight?
Priority chooses the preferred group first; weight influences distribution between records within that same priority.
Why does an SRV lookup return no data at the root domain?
SRV records use service-specific names such as _sip._tcp.example.com.