dneuman64 opened a new issue #2628: golang DNSSEC key creation creates invalid 
keys
URL: https://github.com/apache/trafficcontrol/issues/2628
 
 
   When DNSSEC keys are created by the golang route they are invalid and choke 
TR.  It looks like the domain name is being generated with two periods at the 
end which is causing the issue. 
   
   Example: ```"name": "neuman-test.cdn.domain.com..",
             "expirationDate": 1535907835,
             "inceptionDate": 1533315835,
             "effectiveDate": 1533315835,```
   
   which causes this error in TR: 
   
   ```FATAL 2018-08-03T16:02:39.281 [pool-292-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.dns.SignatureManager - 
org.xbill.DNS.TextParseException: 'neuman-test.cdn.comcast.net..': invalid 
empty label
   org.xbill.DNS.TextParseException: 'neuman-test.cdn.comcast.net..': invalid 
empty label
       at org.xbill.DNS.Name.parseException(Name.java:172)
       at org.xbill.DNS.Name.<init>(Name.java:251)
       at org.xbill.DNS.Name.<init>(Name.java:288)
       at 
com.comcast.cdn.traffic_control.traffic_router.core.dns.DnsSecKeyPairImpl.<init>(DnsSecKeyPairImpl.java:68)
       at 
com.comcast.cdn.traffic_control.traffic_router.core.dns.SignatureManager$1.run(SignatureManager.java:134)
       at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
       at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
       at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
       at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
       at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
       at java.lang.Thread.run(Thread.java:745)```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to