- priority: 5 --> 8
Hi all,
first, i must say, dproxy is a really cool
piece of software.
I have some "special" requirement , that
i deceided to bring dproxy into discussion in a
project. I`m testing for some days now (also included
the reverse lookup bugfix (--> hostnames with "-"
won't resolve correctly) and still recognised, there
seems to be a bug with reverse lookup.
i.e.:
If i have:
server_a is 10.0.0.22
server_b is 10.0.0.222
reverse lookup "10.0.0.22" gives me "server_b" as a
result (in some cases) - depends on the position of
server_a/server_b in the cachefile.
I think the IP-Comparison in the code must have some
sort of "design-flaw". (didn't study yet, but maybe
some form of simple substring comparison??)
Can someone acknowlede this behaviour ?
I'm not very good at programming, but maybe i can fix
this by myself. Perhaps someone other already knows
and has already a fix?
This bug renders dproxy completely usesless for me....
:(
regards
roland