You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2007/05/15 15:04:16 UTC
[jira] Resolved: (JSPF-50) Current dnsjnio resolver fails to
resolve CNAMEd names.
[ https://issues.apache.org/jira/browse/JSPF-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara resolved JSPF-50.
---------------------------------
Resolution: Fixed
Written an asynchronous version of dnsjava Lookup and submitted it to the dnsjnio project.
http://sourceforge.net/tracker/index.php?func=detail&aid=1713970&group_id=194284&atid=948814
*WHEN* it will be accepted into dnsjnio we'll be able to release a proper jspf.
> Current dnsjnio resolver fails to resolve CNAMEd names.
> -------------------------------------------------------
>
> Key: JSPF-50
> URL: https://issues.apache.org/jira/browse/JSPF-50
> Project: jSPF
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.9b4
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Fix For: 0.9.5
>
>
> Dnsjava automatically recurse into CNAME resolution before returning (this process involve also caching).
> Dnsjnio instead returns the empty record with the CNAME row, leaving this task to the client: should we have dnsjnio patched or handle the CNAME case on the client, too?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org