Serge Knystautas wrote:
the case. Personally, I'd prefer to stick with a dnsjava, and can agree
with Stefano that we could expose the DNSServer service and use it,
rather
than call the static methods in dnsjava directly.
I don't see how we could drop use of dnsjava. The SPI only allows
standard hostname to IP address lookups to be handled by a 3rd party
library. The whole reason we got dnsjava in the first place is to be
able to query MX records, and AFAIK, we still cannot do that. Maybe
JNDI, but I didn't think so.
We don't want to drop the use of dnsjava.
The proposal was only to avoid static calls to DNSServer by replacing it
with dependencies on the DNSServer component and non-static calls.
Also, AFAIK SPF information in the TXT record, so dnsjava should have
no trouble retrieving that record type. jSPF would largely just be
parsing of that TXT record into the appropriate rule set, no? If it
intends to do more, it would almost have to depend on dnsjava to be
able to get those TXT records, I would think.
An SPF type has been approved, too.
In jspf we currently support the TXT version because dnsjava does not
handle the SPF record type (99).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
