DNS Domain not updating

[Ronald Lucas]

Using Istanbul...

I'm trying to troubleshoot why some CIs have "DNS Domain" populated while others do not.

In one case, I have a Windows Server CI with "DNS Domain" already populated.   So I blanked out the "DNS Domain" field and saved my changes assuming the next discovery would populate the "DNS Domain" field again.   After that CIs next discovery, the value for "DNS Domain" did not come back...it is still blank.

So I deleted the Windows Server CI completely and discovered it again from scratch.   This time the "DNS Domain" field is populated.   But if I blank out "DNS Domain" again, rediscover it, "DNS Domain" is still blank.

For Windows Server CIs (and maybe others), why would "DNS Domain" only be populated when the CI is created and not updated during subsequent discovery jobs?

Thanks,

Ron

[Dave Mau]

Ron,

This could be related to Probe Caching:

Probe result cache

We cache certain probes we don't think will change often.   If you turn this off either globally or per probe then re-run a discovery it should update the CI.

-Dave

[Ronald Lucas]

Hi Dave.

I'm not sure which probe updates the dns_domain field, so I looked at all probes with "DNS" in the name.   All of them have "Cache results" false.   If you can think of another probe which updates dns_domain, please let me know, and I'll check its "Cache results" setting.

Thanks,

Ron

[Dave Mau]

Check is Discovery > Properties > Probe Caching is on by default.   Search for cache, you would need to uncheck it here, then the settings on the individual probes would be used.

[Ronald Lucas]

Looks like we had already disabled "Use probe cache results" long ago.       And the table discovery_probe_results_cache contains no records.   So I think this confirms this is not a caching issue.

I will look into reconciliation rules to see if something there is causing this field not to update.

Thanks.