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 GitHub Bot (JIRA)" <ji...@apache.org> on 2015/07/01 20:42:05 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=14610802#comment-14610802 ]
ASF GitHub Bot commented on TS-3237:
------------------------------------
Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/238#issuecomment-117792235
@zwoop you said to run clang-format, but when I do there are LOTS of changes to this file-- so I assume we aren't using the default standard clang picks? I searched and can't seem to find where we define which standard we use.
> 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)