[
https://issues.apache.org/jira/browse/TS-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610801#comment-14610801
]
ASF GitHub Bot commented on TS-3237:
------------------------------------
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/238
Revert "TS-3237: Don't segregate DNS results by port."
Fixes: TS-3720
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/238.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #238
----
commit 1c62b35945ce918f1ff89a92314939262e5baba2
Author: Thomas Jackson <[email protected]>
Date: 2015-07-01T18:35:10Z
Revert "TS-3237: Don't segregate DNS results by port."
Fixes: TS-3720
----
> DNS host entries are tied to ports
> ----------------------------------
>
> Key: TS-3237
> URL: https://issues.apache.org/jira/browse/TS-3237
> Project: Traffic Server
> Issue Type: Bug
> Components: HostDB
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Fix For: 5.3.0
>
>
> When HostDB does a DNS resolution of an FQDN it stores it in the HostDB as
> associated with a specific port. This means if the same FQDN is accessed via
> multiple ports (e.g., 80 and 443) there is a duplicate record for each port.
> For normal (that is, non SRV) resolution the port should be fixed to 0
> because the data will always be identical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
