Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Clean up duplicate DNS records of vCenter (76406)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 7683Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Duplicate DNS records after configuring a vCenter Server High Availability environment might interrupt access to the vCenter Server system.

Cause

After configuring or patching a vCenter Server High Availability environment followed by a failover, access to the vCenter Server system might be blocked due to duplicate DNS records for the vCenter Sever Appliance.

Resolution

The issue is resolved in 6.7U3b release of the product. Please ensure before patching vCenter Server High Availability environments, clean up duplicate DNS records from the DNS Server

Workaround

To workaround the issue, follow the below steps:

Note: This is applicable to versions 6.7U3 and 6.7U3a.

Remove the DDNS cron file using following command

rm -rf /etc/cron.d/dns_update.cron

Kill the DDNS daemon process using the process ID. The PID can be retrieved using following command.

root@test-ddns [ ~ ]# ps -eaf | grep ddns
root 10632 1 0 08:31 ? 00:00:00 /usr/bin/python
/usr/lib/applmgmt/ddns/py/ddns.py

kill -9 <PID_DDNS>

Remove the DDNS daemon entry from the prestart-applmgmt.sh file.

root@test-ddns [ ~ ]# vi /usr/lib/applmgmt/support/scripts/prestart-applmgmt

Remove following line from the script
102 if isFeatureEnabled DDNS_Updater ; then
103 /usr/bin/python /usr/lib/applmgmt/ddns/py/ddns.py
104 fi

Restart the applmgmt

Service-control –restart applmgmt

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Application Remote Collector が再起動後、7.5 から 8.0 に自動的にアップグレードされる (76412)

KB
•
在 vRealize Automation 7.x 中禁用 Internet Information Services (IIS) 应用程序池回收 (76333)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant