Openfire

Add support for internal DNS "server"

Details

  • Type: New Feature New Feature
  • Status: In Progress In Progress
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 3.6.4
  • Fix Version/s: 3.7.2
  • Component/s: Core
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

Modify DNSUtil so that before actually peforming a DNS SRV lookup it checks in an internal table if for the specified domain exists an entry. This feature will let admins easily create fake DNS entries for s2s communication.

Add a new page to the admin console so that this new functionality can be easily configured.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Gaston Dombiak added a comment -

DNSUtil was modified. Pending work: Create UI to easily configure the internal DNS

Show
Gaston Dombiak added a comment - DNSUtil was modified. Pending work: Create UI to easily configure the internal DNS
Hide
Permalink
Gaston Dombiak added a comment -

Added system property "dnsutil.dnsOverride" to store values of internal DNS. The property will store values in the following encoded format:

{domain, ip address: port}

eg: {myserver.com,100.23.34.1:5269
eg: {myserver.com,100.23.34.1:5269}, {yourserver.com,200.45.2.25:4567}

Show
Gaston Dombiak added a comment - Added system property "dnsutil.dnsOverride" to store values of internal DNS. The property will store values in the following encoded format: {domain, ip address: port} eg: {myserver.com,100.23.34.1:5269 eg: {myserver.com,100.23.34.1:5269}, {yourserver.com,200.45.2.25:4567}
Hide
Permalink
Gaston Dombiak added a comment -

Restart the server after manually setting the above property.

Show
Gaston Dombiak added a comment - Restart the server after manually setting the above property.
Hide
Permalink
LG added a comment -

"eg: {myserver.com,100.23.34.1:5269}, {yourserver.com,200.45.2.25:4567}" is afaik wrong. The code is very simple and fails to split the values correctly, the space character between "5269}," and "{yourserver" is detected as the server name. I think the user should still be able to use space characters but one should remove all before splitting this string.

Show
LG added a comment - "eg: {myserver.com,100.23.34.1:5269}, {yourserver.com,200.45.2.25:4567}" is afaik wrong. The code is very simple and fails to split the values correctly, the space character between "5269}," and "{yourserver" is detected as the server name. I think the user should still be able to use space characters but one should remove all before splitting this string.

People

Vote (4)
Watch (3)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.