- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-11-2021 11:17 AM
Using Discovery to populate CMDB and it puts DNS name in CIs name field but it's not always accurate so how do I make discovery to insert FQDN instead?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-11-2021 01:04 PM
Understood. What is the source of truth for a ci name? NBT, WMI?
There are couple more properties available to address this issue. You can play around with them to see if it suffice.
glide.discovery.hostname.wmi_trusted
glide.discovery.domain.name.nbt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-12-2021 12:18 AM
Aren't these other answers just masking your underlying problem that DNS is wrong? I don't see the point in just having a correct name in the CMDB if your forward/reverse DNS lookups are wrong.
My vote is figure out why your DNS isn't being maintained accurately and fix that.
Maybe I'm missing something?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-12-2021 05:20 AM
I think you're right here, and moreover this would be a best solution overall. However sometimes this is not feasible for some reasons... maybe system admins are moving too slow or reluctant to make changes. In this case, a cmdb/discovery admin has these tools to address it and have an accurate CMDB in a meantime.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-12-2021 05:25 AM
Yes, I know that but I don't manage that so trying to fix CMDB from Discovery to maintain accurate CI info
