You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/12/16 01:42:13 UTC

[jira] [Commented] (TS-3237) DNS host entries are tied to ports

    [ https://issues.apache.org/jira/browse/TS-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247504#comment-14247504 ] 

ASF subversion and git services commented on TS-3237:
-----------------------------------------------------

Commit a8d186224bd5aab95c0d087da251aefb46ba2af9 in trafficserver's branch refs/heads/master from [~amc]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=a8d1862 ]

TS-3237: Don't segregate DNS results by port.


> 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
>             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)