ADVERT
SRV Record Checker
Query SRV records to map protocols and ports to hostnames for services like SIP, XMPP, LDAP, and more.
How to use this tool
- Query using the _service._proto.example.com format.
- Inspect priority, weight, port, target, and TTL values in returned records.
- Validate target hosts with follow-up A/AAAA lookups before rollout.
Service discovery checks
- Confirm service endpoints for SIP, XMPP, LDAP, and custom protocols.
- Review priority/weight behavior for load distribution and failover.
- Ensure firewall and network rules match advertised service ports.
Operational guidance
- Lower priority values are preferred before higher values.
- Weights apply among records sharing the same priority level.
- Use TTL timing to plan migration windows and endpoint cutovers.
FAQ
- Why do SRV queries return NXDOMAIN for some names?
- SRV hostnames must include both service and protocol labels with underscores, such as _sip._tcp.example.com.
- How are SRV weights interpreted?
- Weights are relative traffic shares among records at the same priority.
- Do clients cache SRV answers?
- Yes, clients and resolvers generally cache according to record TTL values.
ADVERT
ADVERT