PTR records for 209.112.114.33:
| Record | Type | Value | TTL |
|---|---|---|---|
| 33.114.112.209.in-addr.arpa | PTR | dns1.cscdns.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns2.domainnetwork.se. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns3.ascio.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns1.netnames.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | indom10.indomco.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | g4.nstld.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns2.euro909.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns2.dnsvisa.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | a21.verisigndns.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | pdns1.cscdns.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns0.netnames.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns5.netnames.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | a2.verisigndns.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | a23.verisigndns.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | indom30.indomco.fr. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns3.netnames.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns7.netnames.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | k4.nstld.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | f4.nstld.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | l4.nstld.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | indom130.indomco.org. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns1.ascio.net. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | a22.verisigndns.com. | 900 |
| 33.114.112.209.in-addr.arpa | PTR | ns2.webipdns.com.au. | 900 |
id 45157, opcode QUERY, rcode NOERROR, flags QR RD RA ;QUESTION 33.114.112.209.in-addr.arpa. IN PTR ;ANSWER 33.114.112.209.in-addr.arpa. 900 IN PTR dns1.cscdns.net. 33.114.112.209.in-addr.arpa. 900 IN PTR ns2.domainnetwork.se. 33.114.112.209.in-addr.arpa. 900 IN PTR ns3.ascio.net. 33.114.112.209.in-addr.arpa. 900 IN PTR ns1.netnames.net. 33.114.112.209.in-addr.arpa. 900 IN PTR indom10.indomco.com. 33.114.112.209.in-addr.arpa. 900 IN PTR g4.nstld.com. 33.114.112.209.in-addr.arpa. 900 IN PTR ns2.euro909.com. 33.114.112.209.in-addr.arpa. 900 IN PTR ns2.dnsvisa.com. 33.114.112.209.in-addr.arpa. 900 IN PTR a21.verisigndns.com. 33.114.112.209.in-addr.arpa. 900 IN PTR pdns1.cscdns.net. 33.114.112.209.in-addr.arpa. 900 IN PTR ns0.netnames.net. 33.114.112.209.in-addr.arpa. 900 IN PTR ns5.netnames.net. 33.114.112.209.in-addr.arpa. 900 IN PTR a2.verisigndns.com. 33.114.112.209.in-addr.arpa. 900 IN PTR a23.verisigndns.com. 33.114.112.209.in-addr.arpa. 900 IN PTR indom30.indomco.fr. 33.114.112.209.in-addr.arpa. 900 IN PTR ns3.netnames.net. 33.114.112.209.in-addr.arpa. 900 IN PTR ns7.netnames.net. 33.114.112.209.in-addr.arpa. 900 IN PTR k4.nstld.com. 33.114.112.209.in-addr.arpa. 900 IN PTR f4.nstld.com. 33.114.112.209.in-addr.arpa. 900 IN PTR l4.nstld.com. 33.114.112.209.in-addr.arpa. 900 IN PTR indom130.indomco.org. 33.114.112.209.in-addr.arpa. 900 IN PTR ns1.ascio.net. 33.114.112.209.in-addr.arpa. 900 IN PTR a22.verisigndns.com. 33.114.112.209.in-addr.arpa. 900 IN PTR ns2.webipdns.com.au. ;AUTHORITY ;ADDITIONAL
whatsmydns.net PTR Record Lookup tool lets you query DNS servers and get instant results.
Reverse DNS or PTR record lookups are used to determine the PTR records associated with a domain.
Looking for easier to understand results? Use the Global DNS Checker tool.
PTR records, known as Pointer records or reverse DNS records are used to store the domain name for an IP address.
PTR records are the inverse record of both A records for IPv4 addresses, and AAAA records for IPv6 addresses.
PTR records are stored as their IP address broken into segments and then reversed, followed by either .in-addr.arpa. for IPv4 records or .ip6.arpa. for IPv6 records. For example the IP address 192.168.2.1 would be stored in 1.2.168.192.in-addr.arpa..
The Reverse DNS Lookup tool allows you to analyse domain name and IP address configurations in a more comprehensive way than a simple PTR record lookup.
You can use the Reverse DNS Generator to convert IP addresses into the correct format for PTR records.
An example PTR record may look like the following:
| Record | Type | Value | TTL |
|---|---|---|---|
| 1.2.168.192.in-addr.arpa. | PTR | example.com | 3600 |
1.2.168.192.in-addr.arpa. represents identifier of the record. This is the record name for the IPv4 A record 192.168.2.1.
PTR is the record type.
example.com is the value of the record.
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.
| Record | Type | Value | TTL |
|---|---|---|---|
| 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. | PTR | example.com | 3600 |
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. represents identifier of the record. This is the record name for the IPv6 AAAA record fe80::1.
PTR is the record type.
example.com is the value of the record.
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.
