Discovery is not populating the FQDN field.

[MonzaniWill]

After running Discovery on new Linux Servers, the FQDN field is not being automatically filled in although it is possible to find the DNS and populate this information in the Host Name.

Apparently this seems to happen with these new ICs in particular, for other items the information is updated or created normally.

[Anshu_Anand_]

Check out this KB.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827971

Marks answer helpful/correct if it helps you

[MonzaniWill]

This is a Linux Red Hat  9.4, and the command "hostname -f" works fine. I still facing this problem.

[Anshu_Anand_]

Does this command from servicenow returns the results.

Generally FQDN = hostname+DNS domain

I mean when you see the discovery pattern execution, there is a step which populates it.

Try to debug the pattern and check if the FQDN is returning.

Also

There is a system property defined based on which the host_name can also be appended with domain name.

The system property is

glide.discovery.hostname.include_domain

Include domain name in host name: If "yes", include the domain name as part of the host name.  For example, "bosco.service-now.com" instead of "bosco".

There is also a system property which determines the case

glide.discovery.hostname.case

Host name case: If "Lower case" is selected, always translate the host name into lower case; if "Upper case" is selected, always translate the host name to upper case; if "No change" is selected, leave the host name intact. This primarily affects host names discovered with NETBIOS, though some non-standard DNS systems may also return some or all of the name in upper case.

 We also have another system property which defines the fqdn based on regex.

https://www.servicenow.com/community/itom-forum/relation-between-host-name-name-and-fqdn-in-cmdb/m-p...