rimashah25 commented on a change in pull request #4934:
URL: https://github.com/apache/trafficcontrol/pull/4934#discussion_r467179716



##########
File path: 
traffic_portal/app/src/common/modules/form/deliveryServiceStaticDnsEntry/form.deliveryServiceStaticDnsEntry.tpl.html
##########
@@ -57,9 +57,12 @@
                 </div>
             </div>
             <div class="form-group" ng-class="{'has-error': 
hasError(dsStaticDnsEntryForm.address), 'has-feedback': 
hasError(dsStaticDnsEntryForm.address)}">
-                <label for="address" class="control-label col-md-2 col-sm-2 
col-xs-12">Address *</label>
+                <label for="address" class="has-tooltip control-label col-md-2 
col-sm-2 col-xs-12">Address *<div class="helptooltip">
+                    <div class="helptext">The Address Rules.<br>1. 
Type:A_RECORD, Address should be an IPv4 address. <br>2. Type: AAAA_RECORD, 
Address should be an IPv6 address. <br>3. Type: CNAME, Address must end with a 
trailing period if type:CNAME. Eg: cdn.test.com. is correct but cdn.test.com 
will not work</div>

Review comment:
       Yeah, i'll change it.
   

##########
File path: docs/source/api/v2/staticdnsentries.rst
##########
@@ -133,7 +133,7 @@ Creates a new, static DNS entry.
 
 Request Structure
 -----------------
-:address:      If ``typeId`` identifies a ``CNAME`` type record, this is the 
Canonical Name (CNAME) of the server, otherwise it is the IP address to which 
``host`` shall be resolved
+:address:      If ``typeId`` identifies a ``CNAME`` type record, this is the 
Canonical Name (CNAME) of the server that is required to end with a trailing 
period (eg:cdn.test.com. is the right usage but cdn.test.com will throw an 
error), otherwise it is the IP address to which ``host`` shall be resolved

Review comment:
       Ok!




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to