You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Ryan Durfey (JIRA)" <ji...@apache.org> on 2017/06/13 20:17:00 UTC

[jira] [Updated] (TC-353) Can't CNAME hostname with "ccr"

     [ https://issues.apache.org/jira/browse/TC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Durfey updated TC-353:
---------------------------
    Labels: cname configuration host_regex  (was: )

> Can't CNAME hostname with "ccr"
> -------------------------------
>
>                 Key: TC-353
>                 URL: https://issues.apache.org/jira/browse/TC-353
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 1.8.0, 2.0.0, 2.1.0
>            Reporter: Steve Malenfant
>            Priority: Minor
>              Labels: cname, configuration, host_regex
>
> If you put a HOST_REGEX of "ccr.example.kabletown.net", it will expand to the server hostname like "edge01.example.kabletown.net". This makes the remap.config to have the wrong hostname. This might not affect anything but it should be changed to something unrelated to a specific prefix.
> The code ConfigFile.pm is causing the current behavior :
> {code}
> 				my $hname = $ds_type =~ /^DNS/ ? "edge" : "ccr";
> 				my $portstr = "";
> ...
> 	$map_from =~ s/ccr/$host_name/;
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)