another problem with dnscache.

["The Almighty Pegasus Epsilon" <pegasus@pimpninjas.org>]

maybe i'm doing this wrong, but i don't think so, honestly...

 $ grep -E . servers/*172*
servers/16.172.in-addr.arpa:127.0.0.1
servers/16.172.in-addr.arpa:
172.16.0.4
servers/172.16:127.0.0.1
servers/172.16:172.16.0.4
$ dnsname 172.16.0.4

$ dnsq ptr 4.0.16.172.in-addr.arpa
 127.0.0.1
12 4.0.16.172.in-addr.arpa:
178 bytes, 1+1+2+2 records, response, authoritative, noerror
query: 12 4.0.16.172.in-addr.arpa
answer: 4.0.16.172.in-addr.arpa 86400 PTR 
dns1.my.net
authority: 16.172.in-addr.arpa 259200 NS dns1.my.net
authority: 16.172.in-addr.arpa 259200 NS dns2.my.net
additional: 
dns1.my.net 259200 A 172.16.0.4
additional: dns2.my.net 259200 A 172.16.0.29

dnsname provides exactly no answer. /etc/resolv.conf points to dnscache. apparently, according to dnscache, there is no PTR record for that IP address.
 
i don't see a particular difference between that query and this one:

$ dnsname 4.2.2.2
vnsc-bak.sys.gtei.net
$ dnsq ptr 2.2.2.4.in-addr.arpa
 dnsauth1.sys.gtei.net
12 2.2.2.4.in-addr.arpa:
190 bytes, 1+1+3+3 records, response, authoritative, noerror
query: 12 2.2.2.4.in-addr.arpa
answer: 2.2.2.4.in-addr.arpa
 86400 PTR vnsc-bak.sys.gtei.net
authority: 2.2.4.in-addr.arpa 86400 NS dnsauth1.sys.gtei.net
authority: 2.2.4.in-addr.arpa 86400 NS 
dnsauth2.sys.gtei.net
authority: 2.2.4.in-addr.arpa 86400 NS dnsauth3.sys.gtei.net
additional: 
dnsauth1.sys.gtei.net 1800 A 4.2.49.2
additional: dnsauth2.sys.gtei.net 1800 A 4.2.49.3
additional: 
dnsauth3.sys.gtei.net 1800 A 4.2.49.4

so i'm guessing it's something incorrect in the servers directory. i did, for the record, restart dnscache after adding the 172.16 and 16.172.in-addr.arpa
 files to the servers directory.