-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.21.0, 4.22.0
-
None
Description of problem:
AWS DNS resolver needs to be included in the no_proxy. I found this during the investigation of a different issue found in custom-dns and realized this needed to be updated.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: