Difference between revisions of "Flushing vCenter DNS cache"
From Notes_Wiki
(Created page with "<yambe:breadcrumb>VMWare_vCenter|VMWare vCenter</yambe:breadcrumb> =Flusing vCenter DNS cache= # ssh to vcenter # Run this command to restart resolver #:<pre> #:: systemct...") |
m |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[Flushing vCenter DNS cache]] | |||
# ssh to vcenter | # ssh to vcenter | ||
Line 6: | Line 5: | ||
#:<pre> | #:<pre> | ||
#:: systemctl restart systemd-resolved.service | #:: systemctl restart systemd-resolved.service | ||
#:<pre> | #:</pre> | ||
# Test with nslookup, if issue is still there continue | # Test with nslookup, if issue is still there continue | ||
# Run following command and check if 127.0.0.1 is listed as preferred nameserver | # Run following command and check if 127.0.0.1 is listed as preferred nameserver | ||
Line 28: | Line 27: | ||
[[Main_Page|Home]] > [[VMWare platform]] > [[VMWare vCenter]] > [[Flushing vCenter DNS cache]] |
Latest revision as of 08:55, 7 April 2022
Home > VMWare platform > VMWare vCenter > Flushing vCenter DNS cache
- ssh to vcenter
- Run this command to restart resolver
- systemctl restart systemd-resolved.service
- Test with nslookup, if issue is still there continue
- Run following command and check if 127.0.0.1 is listed as preferred nameserver
- cat /etc/resolv.conf
- Run following command and check name of service (most probably dnsmasq)
- netstat -alnp | grep 53
- Restart dnsmasq using:
- systemctl restart dnsmasq
- Again test with nslookup and verify that old cached entry is not present
Refer:
Home > VMWare platform > VMWare vCenter > Flushing vCenter DNS cache