Details
-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13, 4.12, 4.11, 4.14, 4.15, 4.16
-
Moderate
-
Yes
-
Rejected
-
False
-
Description
Description of problem:
In dual stack cluster where IPv6 address also present the dns server address for upstreamresolver is configured in Upper case instead normal case. It was identified in automation runs initially. In the forwardplugin configuration, we can see it is not in upper case.
forwardplugin
7-ocp52077.ocp:5353 {
27- prometheus 127.0.0.1:9153
57: forward . fd01:0:0:6::6b { <----------------------
88- policy sequential
114- }
120- errors
131- log . {
143- class error
163- }
upstreamresolver
.:5353 { bufsize 1232 errors log . { -- lameduck 20s } ready kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure fallthrough in-addr.arpa ip6.arpa } prometheus 127.0.0.1:9153 forward . [FD01:0:0:6::6B]:53 { <----------- policy sequential } cache 900 { denial 9984 30 } reload -- hostname.bind:5353 { chaos
we are trying to create a forwarding DNS requests over TLS/CLEAR TEXT.
According RFC https://www.rfc-editor.org/rfc/rfc5952#section-4.3 standard, the configuration should not be case sensitive.
Version-Release number of selected component (if applicable):
How reproducible:
https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-52077
Steps to Reproduce:
1. Edit the dns operator with transport option as Cleartext for upstreamresolver $ oc edit dns.operator default spec: upstreamResolvers: policy: Random transportConfig: transport: Cleartext upstreams: - type: Network address: <dns-server ip> 2. Check the configmap or check /etc/coredns/Corefile in the coredns oc get cm dns-default -n openshift-dns -o yaml
Actual results:
In the core file the dns server address is automatically coming in upper case with a square bracket in upstreamresolver configuration [FD01:0:0:6::6B]:53
Expected results:
It is should also be in lower case like how it comes in forwardplugin configuration fd01:0:0:6::6b
Additional info: