Service Mapping: Map shows Incorrect connection / relationship from Load Balancer to the Windows ServerIssue This KB article is to show how to check why the Service Mapping maps shows incorrect connection / relationship from Load Balancer to the Windows Server given that the patterns payload / discovery returns correct connection / relationship.CauseThe reason why the Windows Server ends in DNS cluster of the Load Balancer is because there is a record in the DNS mapping table [cmdb_ci_dns_name]. DNS cluster logic is to map same IP that resolved from different host names.If we lookup by IP xx.xxx.xx.xxx, it shows multiple records, where duplicate host names can be found. Therefore there are more than one distinct host names. These records creates the DNS cluster. - Query on [cmdb_ip_address_dns_name] table where ip_address.ip_address = 'xx.xxx.xx.xxx'. Run nslookup on the hostname, check if it returns different IPs.This means that the records in 'cmdb_ip_address_dns_name' are outdated. Resolution1. Remove the records found from the query / URL below: Replace the <instance-name> with the actual instance name Replace the xx.xxx.xx.xxx with the IP Address. https://<instance-name>.service-now.com/cmdb_ip_address_dns_name_list.do?sysparm_query=ip_address.ip_address%3Dxx.xxx.xx.xxx 2. Run Discovery on the Application Service. 3. Map should be updated.