Check SRV records instantly across global resolvers to validate your service discovery, ports, and load balancing rules.
Unlike standard records, SRV records require a very specific query format. To check an SRV record, you must include the service and protocol in your lookup (e.g., _sip._tcp.example.com). Enter your properly formatted service domain above to instantly query its active SRV records.
_) and be separated by a dot.server1.example.com). This target MUST resolve to an A or AAAA record. If the target points to a CNAME, the SRV configuration is invalid according to DNS standards.What do all those numbers mean? Learn the exact anatomy of an SRV record, how ports are defined, and why you can never use a CNAME as a target.
Read the SRV Record WikiSRV records define the location of services like SIP, XMPP, LDAP, and other protocols. They specify priority, weight, port, and target host. SRV lookups are critical when troubleshooting service discovery or verifying that a client can find the correct service endpoint.
Common issues include wrong service names, incorrect protocol labels, or missing target records. The SRV name follows a strict format: _service._proto.host. If any part is wrong, lookup fails. Also ensure the target host resolves to A or AAAA records.
If you need related checks, try A record lookup and TXT record check tool.
Priority chooses which servers are preferred, and weight distributes load among servers with the same priority.
It is _service._proto.hostname. For example, _sip._tcp.example.com.
Yes. The target is a hostname that must resolve to an IP address via A or AAAA.
Check the service and protocol labels, the exact hostname, and verify that the SRV record exists at the correct location.
Some resolvers do not follow CNAMEs in SRV lookups. Use direct hostnames for the target if possible.
Short TTLs can help during changes, but stable services often use longer TTLs for caching.