GitHub user fnavidan edited a comment on the discussion: VM instances get VR's IP as DNS server but cannot resolve through VR
I have tried restarting network with cleanup many times. Sometimes both DHCP and DNS services are not deployed on VR and sometimes only DNS service is unavailable. I tried one more time now and realized DHCP is working but not DNS. I am considering upgrade to 4.20.2 LTS. However, I'm not sure if I can directly upgrade from 4.18.2 to 4.20.2 or I should first go for 4.18.2 to 4.19.x. For your reference: After network restart, inside a VM: # dig @149.50.127.132 google.com ; <<>> DiG 9.11.36-RedHat-9.11.36-16.el8_10.4 <<>> @149.50.127.132 google.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached GitHub link: https://github.com/apache/cloudstack/discussions/11749#discussioncomment-14792430 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
