Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

Re: Reverse DNS tool not working?

$
0
0

Reverse DNS FAQ | DNSstuff


First, ALL of the below is based on the presumption that the zone has been properly delegated.


After several tests, retests, pondering, rinsing and repeating, here's what I'm observing:


If I do a generic query for a PTR record of one of the above four addresses, I get mixed results, depending on which of your DNS servers was allegedly queried.

Sometimes, but very rarely, I get a positive response from a generic query.

 

If I force the query to a specific DNS server (I tested both 158.106.84.10 and 158.106.84.11), I get valid responses every time.

This is the result of a forced query to 158.106.84.10. Only ONE response is an expected condition in a directed query.

10-16-2014 7-30-27 PM.png

 

But here, I sent a generic query. It failed.

10-16-2014 7-29-16 PM.png

10-16-2014 7-31-43 PM.png

FWIW, I do not have this behavioral issue when querying my own IP Address, the IP Address of DNSStuff.com, or the IP Address of Solarwinds.com, so I do not believe it is an issue with DNSStuff.com

 

I would suggest monitoring the traffic across port 53 while initiating another series of queries, and see if ALL of the queries are crossing your threshold.

Also, enable logging on all of the DNS Servers and see who/if/when queries are received and/or responses are generated.

The missing link at this point is identifying exactly when/why the lookup fails.

10-16-2014 7-27-34 PM.png

10-16-2014 7-27-55 PM.png

10-16-2014 7-28-28 PM.png


Viewing all articles
Browse latest Browse all 20396

Trending Articles