Closed clincha closed 1 year ago
Alright it looks like a PITA to get these working together. Time for firewalld to go. At some point I might want to move to another OS (ubuntu?) to get this working
Disabling the firewall worked. Unfortunately, it will need to stay like this until I either want to sink the time to configure it or change the infrastructure to support it
61 identified DNS resolution issues. I thought that I had resolved the problem but it has cropped up again in a later deployment.
The issue seems in part to relate to the issues in this StackOverflow post. I'm using the OS they are having problems with and manually disabling firewalld allows DNS traffic to resolve again. When firewalld is running I get these errors in the core-dns logs:
It looks like firewalld is blocking the route to the gateway for DNS lookups. I would prefer to have firewalld running but DNS traffic allowed through it. Lets see what we can do.