No SRV records found for 251.195.156.
Try 195.156 instead?
id 30125, opcode QUERY, rcode NXDOMAIN, flags QR RD RA ;QUESTION 251.195.156. IN SRV ;ANSWER ;AUTHORITY . 86394 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024111401 1800 900 604800 86400 ;ADDITIONAL
whatsmydns.net SRV Record Lookup tool lets you query DNS servers and get instant results.
Service Records or SRV record lookups are used to determine the SRV records associated with a domain.
Looking for easier to understand results? Use the Global DNS Checker tool.
SRV records, known as Service records are used to store information relating to hostname, port and protocol details for applications or services which are serviced by the domain.
For example, SRV records can be used to store the location of services required for Internet applications such as Voice over Internet Protocol (VoIP) or messaging services using the Extensible Messaging and Presence Protocol (XMPP)
An example SRV record may look like the following:
| Record | Type | Priority | Weight | Port | Target | TTL |
|---|---|---|---|---|---|---|
| _sip._tcp.example.com | SRV | 10 | 20 | 5060 | sip1.example.com | 3600 |
_sip._tcp.example.com represents identifier of the record. This is broken down further into 3 sections. _sip represents the name of the service. _tcp represents the protocol of the service, this is usually either TCP or UDP. example.com represents the domain in which this record is for.
SRV is the record type.
10 is the priority of the record. The lower the value, the higher the priority.
20 is the weight of the record. This is the weight of which this record has a chance to be used when there are multiple matching SRV records of the same priority.
5060 is the port of the record. This specifies the port on which the application or service is running.
sip1.example.com is the target of the record. This specifies the domain of the application or service the record is for. SRV records must specify a target which is either an A record or AAAA record, and may not use CNAME records.
3600 is the TTL (time to live) of the record in seconds, this example represents 1 hour. This means that when a record has had updates made to it, then it will take 1 hour to update.
