Persistent inverse query

[mikewise99 at my-deja.com]

For some reason (no doubt having to do with the way I have things
configured) my named keeps doing inverse queries, thereby triggering my
Dial-on-demand ISDN line and spending money. Not good. I turned on query
logging and got the following:

09:20:16 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:20:16 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:20:55 .. XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:20:55 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:21:05 ...XX /192.168.25.1/www.twinwave.net/A
09:21:05 ...XX /192.168.25.1/mail.twinwave.net/A
09:22:20 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:22:25 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:22:30 ...XX /192.168.25.1/255.255.255.255.in-addr.arpa/PTR
09:22:40 ...XX /192.168.25.1/www.twinwave.net/A
09:22:40 ...XX /192.168.25.1/mail.twinwave.net/A

Notice that the date, server name, and process name has been edited away
to save space.

Can anybody tell me what these reverse lookups are all about? Would it
help if I put added a 255.255.255.255.in-addr-arpa file to my config?
And what would go in such a beast?

BTW, I am running named 4.9.7.-T1B on SuSE Linux 5.3.

TIA,

Mike Wise


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.