PTR records

Follow

joseph.ribera

June 13, 2013 06:06

Hi,

When i'm using openDNS servers i can't reverse look up any addresses in x.74.133.198.in-addr.arpa. If i use google DNS servers i can.  

Is there something wrong with OpenDNS ?

0

• 

  maintenance June 13, 2013 07:14

  In private address space? You probably have the resolver addresses configured on individual devices then, and not in a router or DNS server forwarder. This breaks local name resolution definitely with OpenDNS, since you are sending a LAN query to the internet, and OpenDNS uses nxdomain redirection for filtering purposes. If you are using a paid version, or a free version and you aren't interested in filtering, simply turn this (Typo Correction) off at the Dashboard. I don't think you could reasonably add a list of exceptions for reverse lookups under Exceptions (Exceptions for VPN Users, it is called, due to it's primary/original intent.)

  0

  Comment actions Permalink
• 

  rotblitz June 13, 2013 12:45

  CIDR 198.133.74.0/24 is not in a private IP address space, but assigned to InterSystems Corporation in Cambridge, MA (intersys.com). This corporation as the owner of this range or their ISP is to configure the PTR records. It is not mandatory for IP address owners to configure PTR records anyway. They did not configure a PTR record for all 255 IP addresses, but for some only.

  Are you saying that OpenDNS does not return a PTR record whereas Google does for exactly the same Intersys address? Can you give examples?

  0

  Comment actions Permalink
• 

  joseph.ribera June 13, 2013 22:50

  Hi Rotblitz.

  You are correct, this is a public address space which has PTR records configured for various IP addresses. As an example 198.133.74.1 has a PTR record, if you query this through Google DNS you will get the response below. If you query via open DNS you just get a time out. 

  Server: google-public-dns-a.google.com
  Address: 8.8.8.8

  Non-authoritative answer:
  1.74.133.198.in-addr.arpa name = mail.intersys.com

   

  0

  Comment actions Permalink
• 

  maintenance June 14, 2013 05:16

  Wow, that was a complete reading failure on my part.

  0

  Comment actions Permalink
• 

  jedisct1 June 14, 2013 05:18

  Confirmed:

  $ drill ptr 1.74.133.198.in-addr.arpa. @208.67.222.222

  [timeout]

   

  0

  Comment actions Permalink
• 

  jedisct1 June 14, 2013 05:24

  Two of the three authoritative name servers are failing. ns.uu.net works but uucp-gw-1.pa.dec.com and uucp-gw-2.pa.dec.com don't.

  0

  Comment actions Permalink
• 

  maintenance June 14, 2013 05:44

  Yes, it fails. Using dig, or making sure to add the trailing dot when using nslookup (or increasing the timeout) returns the nxdomain redirect IP from OpenDNS.  67.215.65.132

   

  0

  Comment actions Permalink
• 

  maintenance June 14, 2013 05:49

  and jedisct1 posted twice while I was mucking about.

  0

  Comment actions Permalink
• 

  joseph.ribera June 14, 2013 06:17

  Thanks for confirming.

  Suggestions on how to fix ? Go back to the ISP who manages 74.133.198.in-addr.arpa and tell them to look at the authoritative name servers ?

  0

  Comment actions Permalink
• 

  rotblitz June 14, 2013 09:36

  "Go back to the ISP who manages 74.133.198.in-addr.arpa and tell them to look at the authoritative name servers ?"

  Yes, you got it.

  0

  Comment actions Permalink

Please sign in to leave a comment.