IP Range Scan Discovery - Assets are named by IP, Not picking up DNS Name

[swright]

When an asset is detected, but cannot be scanned it will get added as a Linux device since port 22 is open.  The asset name will be the IP, even though there is a DNS record.  If I scan the IP with Device Tester, it will detect the DNS entry.  Why isn't the the asset added with the DNS name?

I have an on-prem environment linked to Cloud.  My scanners are on-prem with access to DNS.

I've used Flow Builder update the Asset Name with the DNS name, but it will revert back to IP on next scan.  This also happens when I change the Asset Type.  I thought when an override is made to a field, the 'lock icon' is enabled and will prevent a scan from changing back, but this is not the case.

Anyone know how to fix?

[DavidPK · Accepted solution]

Hello there! 

Our tech support team should be able to assist you with this.  Please open a ticket in our support portal.

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.

[swright · Accepted solution]

Ticket opened. Thank you

[DavidPK · Accepted solution]

Hello there! 

Our tech support team should be able to assist you with this.  Please open a ticket in our support portal.

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.