0

Here is my bind query.log:

28-May-2012 13:34:00.370 queries: info: client IINTERNAL_DNS_IP#49428: view internal: query: 44.33.22.11.in-addr.arpa IN PTR + (EXTRENAL_DNS_IP)

28-May-2012 13:34:00.532 queries: info: client IINTERNAL_DNS_IP#50406: view internal: query: 44.33.22.11.in-addr.arpa IN PTR + (EXTRENAL_DNS_IP)

28-May-2012 13:34:00.697 queries: info: client IINTERNAL_DNS_IP#50674: view internal: query: 44.33.22.11.in-addr.arpa IN PTR + (EXTRENAL_DNS_IP)

I am receiving a lot for request from my Internal DNS Server: continuously ask for 11.22.33.44 PTR record. 11.22.33.44 PTR record does not exist, so it cant be cached.

Is any way to cache/block these requests and make extrenal DNS not to create a new query each time? Any idea how to solve this problem?

4
  • 2
    Try to find, why the 11.22.33.44 PTR record is asked rather than find a way to hinding logs.
    – Yohann
    May 28, 2012 at 10:49
  • 11.22.33.44 is a valid web application we have.
    – amprantino
    May 28, 2012 at 11:55
  • And do you have the DNS reverse delegation for this IP range ?
    – Yohann
    May 28, 2012 at 12:33
  • No. I am asking an other (authorative) DNS. The other DNS does not have a PTR record. The DNS admins of 11.22.33.44 told that they dont want a PTR.
    – amprantino
    May 28, 2012 at 13:09

1 Answer 1

0

BIND should be caching the NXDOMAIN response. There's a whole RFC dedicated to negative caching. There's a chance the far-end's zone SOA has the value set too low. Read more on SOA settings, particularly the last number ("min").

You could make a zone "44.33.22.11.in-addr.arpa" on your resolver and assign it data, if you can't get it working another way, but that's super-hacky.

Good luck!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .