Gone through provided pcap files and following are my observations. Moreover, With this only affecting reverse lookups and the pcaps not containing the lookups: After restart of atomic-openshift-node service, still issue persist. Requested you to update the upstream name and check. When we check the /etc/origin/node/nf, there are no entries. We have checked the /etc/nf, /etc/nf & /etc/origin/node/node-config.yaml looks fine. A forward lookup is working fine without any issues and reverse lookup is not working but when try to pointing the upstream name server it's working fine which is concluded that there is no issue with the upstream name server. We have tested the DNS forward and reverse lookup. We have verified that the port 53 is listening and that dnsmasq is the process holding it We have restarted dnsmasq and nothing different happened. This means that the communication between the node and the upstream servers works. We have successfully run "host" resolution commands to the upstream servers from the faulty node. We have checked the dnsmasq configuration and is the same as the rest of the cluster. Customer had one node in your OCP 3.11 cluster that seems to not be able to communicate to the upstream dns servers, Dns resolution is failing on this node consistent, but works on the rest of the cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |