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 ji...@apache.org on 2004/04/20 22:49:53 UTC
[jira] Created: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Unassigned
Priority: Blocker
Project: James
Components:
DNSServer
Versions:
2.2.0RC1
Assignee:
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Tue, 20 Apr 2004 1:48 PM
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Reopened: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
Message:
The following issue has been reopened.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Reopened
Priority: Blocker
Project: James
Components:
DNSServer
Fix Fors:
2.2.0RC2
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Wed, 21 Apr 2004 7:11 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Noel J. Bergman (mailto:noel@devtech.com)
Date: Tue, 20 Apr 2004 1:48 PM
Changes:
environment changed from to dnsjava 1.6.2
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-265?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Unassigned
Priority: Blocker
Project: James
Components:
DNSServer
Versions:
2.2.0RC1
Assignee:
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Tue, 20 Apr 2004 1:48 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Noel J. Bergman (mailto:noel@devtech.com)
Date: Wed, 21 Apr 2004 7:12 PM
Changes:
Fix Version changed to 2.2.0RC2
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-265?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Reopened
Priority: Blocker
Project: James
Components:
DNSServer
Fix Fors:
2.2.0RC2
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Wed, 21 Apr 2004 7:12 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
Message:
The following issue has been re-assigned.
Assignee: Noel J. Bergman (mailto:noel@devtech.com)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Open
Priority: Blocker
Project: James
Components:
DNSServer
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Tue, 20 Apr 2004 8:34 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Closed: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Wed, 21 Apr 2004 2:59 PM
Will be in 2.2.0RC2
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Closed
Priority: Blocker
Resolution: FIXED
Project: James
Components:
DNSServer
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Wed, 21 Apr 2004 2:59 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Closed: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Closed
Priority: Blocker
Resolution: FIXED
Project: James
Components:
DNSServer
Fix Fors:
2.2.0RC2
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Wed, 21 Apr 2004 7:12 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-265) org.xbill.DNS.Address not resolving addresses in some configurations
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Tue, 20 Apr 2004 8:36 PM
Body:
Fixed in CVS. We need to decide if this will be included in the James 2.2.0 release.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JAMES-265?page=comments#action_35174
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JAMES-265
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JAMES-265
Summary: org.xbill.DNS.Address not resolving addresses in some configurations
Type: Bug
Status: Open
Priority: Blocker
Project: James
Components:
DNSServer
Versions:
2.2.0RC1
Assignee: Noel J. Bergman
Reporter: Noel J. Bergman
Created: Tue, 20 Apr 2004 1:48 PM
Updated: Tue, 20 Apr 2004 8:36 PM
Environment: dnsjava 1.6.2
Description:
The DNS code uses org.xbill.DNS.Address to resolve addresses so that we are not impacted by java.net ignoring DNS TTL. dnsjava is not always able to locate default servers. When it cannot, getByName and getAllByName fail.
There is a one line fix to make sure, as we should want anyway, that it always uses the servers provided in the James configuration to resolve DNS information.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org