Bug #15341
Smart Proxy - dnscmd - Case sensitivity issues with MS DNS
Description
In cases where foreman provides a DNS zone that has different casing than the enumerated zones returned by MS DNS, the smart proxy throws an error that there is no authoritative zones.
Associated revisions
History
#1
Updated by The Foreman Bot over 4 years ago
- Status changed from New to Ready For Testing
#2
Updated by Jack Watroba over 4 years ago
#3
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/430 added
#4
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/smart-proxy/pull/431 added
#5
Updated by Jack Watroba over 4 years ago
Just kidding, it's this one: https://github.com/theforeman/smart-proxy/pull/431
#6
Updated by Dmitri Dolguikh over 4 years ago
- Project changed from Foreman to Smart Proxy
- Category set to DNS
#7
Updated by Dmitri Dolguikh over 4 years ago
- Pull request deleted (
https://github.com/theforeman/smart-proxy/pull/430, https://github.com/theforeman/smart-proxy/pull/428)
#8
Updated by Jack Watroba over 4 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e182f9a097e636ca4c15c50e320ed8362f574515.
#9
Updated by Dominic Cleal over 4 years ago
- Assignee set to Jack Watroba
- Legacy Backlogs Release (now unused) set to 161
fixes #15341 - case sensitivity issues with dnscmd