Re: how to reduce traffic caused by lame delegation

> Turn on query-logging and send us the log lines showing these lame domain
> queries.

Hi,

i turned query logging on and got huge amount of the following:

Jul 2 13:27:31 server named[4811]: lame server resolving
'50.88.86.63.in-addr.arpa' (in '88.86.63.in-addr.arpa'?):
209.201.74.14#53
Jul 2 13:27:31 server named[4810]: client internal_ip#52701: query:
32.67.92.195.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52702: query:
6.99.5.217.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52703: query:
133.2.25.194.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52704: query:
33.19.45.216.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52705: query:
130.29.231.194.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52706: query:
88.159.153.62.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: lame server resolving
'34.254.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4811]: lame server resolving
'31.18.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4810]: client internal_ip#52707: query:
58.64.165.213.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52708: query:
199.107.66.66.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: lame server resolving
'194.254.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4811]: client internal_ip#52709: query:
147.172.64.217.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52710: query:
191.44.5.64.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: lame server resolving
'2.16.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4810]: client internal_ip#52711: query:
221.133.146.204.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: lame server resolving
'24.16.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4810]: client internal_ip#52712: query:
198.133.74.216.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: lame server resolving
'15.16.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4810]: client internal_ip#52713: query:
138.217.239.149.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52714: query:
108.131.207.66.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: lame server resolving
'34.0.102.128.in-addr.arpa' (in '102.128.in-addr.arpa'?):
198.116.144.33#53
Jul 2 13:27:31 server named[4811]: client internal_ip#52715: query:
1.0.136.193.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52716: query:
4.236.132.62.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52717: query:
171.0.168.192.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52718: query:
12.251.51.198.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52720: query:
20.1.2.136.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: lame server resolving
'5.78.159.64.in-addr.arpa' (in '78.159.64.in-addr.arpa'?):
64.159.80.3#53
Jul 2 13:27:31 server named[4811]: client internal_ip#52721: query:
145.14.232.202.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4810]: client internal_ip#52722: query:
130.192.176.62.in-addr.arpa IN PTR
Jul 2 13:27:31 server named[4811]: client internal_ip#52723: query:
60.177.125.212.in-addr.arpa IN PTR
Jul 2 13:27:32 server named[4810]: client internal_ip#52724: query:
18.192.184.195.in-addr.arpa IN PTR
Jul 2 13:27:32 server named[4811]: client internal_ip#52725: query:
140.251.197.203.in-addr.arpa IN PTR
Jul 2 13:27:32 server named[4810]: client internal_ip#52741: query:
174.254.185.212.in-addr.arpa IN PTR
Jul 2 13:27:32 server named[4811]: client internal_ip#52742: query:
50.88.86.63.in-addr.arpa IN PTR
Jul 2 13:27:32 server named[4810]: lame server resolving
'5.78.159.64.in-addr.arpa' (in '78.159.64.in-addr.arpa'?):
64.159.80.2#53
Jul 2 13:27:32 server named[4810]: lame server resolving
'50.88.86.63.in-addr.arpa' (in '88.86.63.in-addr.arpa'?):
209.201.74.14#53
Jul 2 13:27:32 server named[4811]: lame server resolving
'50.88.86.63.in-addr.arpa' (in '88.86.63.in-addr.arpa'?):
198.6.1.19#53
Jul 2 13:27:33 server named[4811]: client internal_ip#52744: query:
5.78.159.64.in-addr.arpa IN PTR
Jul 2 13:27:33 server named[4810]: lame server resolving
'5.78.159.64.in-addr.arpa' (in '78.159.64.in-addr.arpa'?):
64.159.80.2#53
Jul 2 13:27:33 server named[4810]: lame server resolving
'5.78.159.64.in-addr.arpa' (in '78.159.64.in-addr.arpa'?):
64.159.80.3#53
Jul 2 13:28:29 server named[4810]: client internal_ip#52748: query:
35.210.12.194.in-addr.arpa IN PTR
Jul 2 13:28:29 server named[4810]: client internal_ip#52749: query:
30.14.33.192.in-addr.arpa IN PTR
Jul 2 13:28:29 server named[4811]: client internal_ip#52750: query:
241.5.5.192.in-addr.arpa IN PTR
Jul 2 13:28:29 server named[4810]: client internal_ip#52751: query:
244.194.87.165.in-addr.arpa IN PTR

The log rises with more than 100 messages per minute querying.....