DNS resolution failed: server IP address could not be found

/etc/hosts file has an entry in my development server 10.xx.xx.162 server-dev.xxx-intra.net. ping to server-dev.xxx-intra.net is successful.But when I am trying to access from the browser – https://server-dev.xxx-intra.net, it throws server-dev.xxx-intra.net’s server IP address could not be found. I understand that it is not able to resolve that name to IP but shouldn’t /etc/hosts entry have…

YUM Upgrade when package name changes

The API Gateway Kong decided to change the name of their Centos package. For versions up to 1.1 its “kong-community-edition”, after that its just “kong” kong-community-edition.noarch 1.0.2-1 bintray–kong-kong-rpm kong-community-edition.noarch 1.0.3-1 bintray–kong-kong-rpm kong-community-edition.noarch 1.1.0rc1-1 bintray–kong-kong-rpm kong.noarch 1.2.1-1 bintray–kong-kong-rpm kong.noarch 1.2.2-1 bintray–kong-kong-rpm kong.x86_64 1.3.0-1 bintray–kong-kong-rpm Can I somehow tell YUM to upgrade the current installation of kong-community-edition…

Verify return code: 20 unable to get local issuer certificate

been following the guide below to create a transparent IoT Edge gateway, and connect a downstream/leaf device to it. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-connect-downstream-device When i reach the final test step as below openssl s_client -connect mygateway.contoso.com:8883 -CAfile /certs/azure-iot-test-only.root.ca.cert.pem -showcerts I got the error below No client certificate CA names sent Client Certificate Types: RSA sign, DSA sign, ECDSA…

“ip route get” gives “No route to host” on linux centos 7.7

I have been investigating root cause of a hairy routing issue on a centos7 cluster… Behavior: TCP packets from Docker Container reach targets outside of the cluster, but response packets do not reach container that is waiting for that answer Using logging of iptables now strongly indicates that “routing decision” (in iptables speak) causes this…