OK, I am making progress of a sort ...
Notice the difference, here:
$ /usr/local/java/bin/java -cp dnsjava-2.0.2.jar lookup
141.22.88.24.query.bondedsender.org
141.22.88.24.query.bondedsender.org:
141.22.88.24.query.bondedsender.org.com. 3417 IN A
216.234.246.154
141.22.88.24.query.bondedsender.org.com. 3417 IN A
216.234.246.155
141.22.88.24.query.bondedsender.org.com. 3417 IN A
216.234.246.153
$ /usr/local/java/bin/java -cp dnsjava-2.0.2.jar dig
141.22.88.24.query.bondedsender.org
; java dig 0.0
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63925
...
Same server, same version of dnsjava, no other code, different lookup
mechanisms. The former exhibits the bad behavior (bogus results), the
latter (NXDOMAIN) is what we want.
So the problem does not appear to be in JAMES, as far as I can tell, but is
in dnsjava. I've tried dnsjava 1.6.2, 2.0.1 and 2.0.2. 1.6.2 works, the
2.x series fails. I can also report that if I use JNDI (trivial driver
attached), it works properly.
This is getting into Brian Wellington territory, so I'm cc'ing him, although
I'll keep digging.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
