ADVERT
🎯 SRV Record Checker
Query SRV records to map protocols and ports to hostnames for services like SIP, XMPP, LDAP, and more.
SRV Record Checker
Discover service locations, ports, and priorities defined by SRV records for SIP, XMPP, LDAP, and custom protocols.
What you'll see
- Priority, weight, port, and target host for every SRV record returned.
- TTL values so you can predict how long clients will cache service endpoints.
- Helper text reminding you to query using the _service._proto.example.com format.
Common use cases
- Verify VoIP or chat workloads before opening firewall ports.
- Confirm Minecraft, Matrix, or other custom services broadcast the correct endpoints.
- Document autodiscovery targets for enterprise software rollouts.
DNS Resolver
Query SRV records to locate services, ports, and priorities for protocols like SIP, XMPP, and more.
Prepared query:
_sip._tcp.example.comTroubleshooting tips
- Lower priority numbers take precedence; clients only evaluate higher values if the first set is unavailable.
- Ensure target hosts resolve with A or AAAA records, otherwise clients cannot connect.
- Keep weights proportional to the traffic share you want each endpoint to receive.
FAQ
- Why does my SRV lookup return NXDOMAIN?
- SRV queries must include the service and protocol, for example _sip._tcp.example.com. Missing the underscores or using the bare domain will return NXDOMAIN.
- How are weight values interpreted?
- Weights are relative shares among records with the same priority. A record with weight 10 will receive twice the traffic of one with weight 5.
- Do clients cache SRV responses?
- Yes. Clients typically respect the TTL reported with the record, so plan changes ahead and lower TTLs when migrating services.
ADVERT
ADVERT