DNSResolutionMonitor incorrectly sets port number

Description

If the nameserver parameter for DNSResolutionMonitor matches the pattern \S+:\d+ (ex: 127.0.0.1:10532), then it does not set the port number correctly.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed April 18, 2019 at 5:41 PM

FYI, I cherry-picked this back to release-24.0.0 since it does at least apply there.

Ron Roskens April 5, 2019 at 3:30 PM

Fixed

Details

Assignee

Reporter

Fix versions

Priority

PagerDuty

Created April 5, 2019 at 3:27 PM
Updated April 18, 2019 at 5:41 PM
Resolved April 18, 2019 at 5:41 PM