[
https://issues.apache.org/jira/browse/TS-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606847#comment-14606847
]
Thomas Jackson commented on TS-3237:
------------------------------------
This is actually okay (that these entries are tied to ports) since the entry is
keeping track of real status. What we need to do (for host files) is override
down when the resolution happens-- against some in memory mapping of the name
-> ip
> 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)
