Jump to content
j-gray

Automatic FQDN rename not working

Recommended Posts

This task has been configured to run on the 'Lost and Found' container for quite a while and has been working. The task still runs successfully, but we have 60+ Mac's that are not updating their FQDN. The show as hostname only.

They reply/resolve on the network with their FQDN. They are in DNS and DHCP with their correct FQDN.

Why does ESMC not show their correct FQDN and what can I do to resolve this issue?

Share this post


Link to post
Share on other sites

Seems that in ESMC 7.0 hostname and FQDN are both extracted from value that can be fetch via command line:

sysctl kern.hostname

Could you verify what value it returns in your environment? There seems to be no "standard" way how to configure macOS after it is joined into domain and this detection seems to work for all users

In previous versions there was also alternative implementation that used reverse-DNS but it results in issues reported by other customers and could possibly lead in reporting completely invalid data -> it was depending on network configuration.

 

Share this post


Link to post
Share on other sites
5 hours ago, MartinK said:

Seems that in ESMC 7.0 hostname and FQDN are both extracted from value that can be fetch via command line:


sysctl kern.hostname

Could you verify what value it returns in your environment? There seems to be no "standard" way how to configure macOS after it is joined into domain and this detection seems to work for all users

In previous versions there was also alternative implementation that used reverse-DNS but it results in issues reported by other customers and could possibly lead in reporting completely invalid data -> it was depending on network configuration.

 

Thanks for the reply.

That command returns the hostname only.

How do we get the client to properly report FQDN?

The problem is that this creates two objects when using AD sync: one object with FQDN and the same object with hostname only. The object with hostname only then gets dumped into Lost & Found.

The rename task used to work in the past. We have too many clients to rename every duplicate manually. Is there a workaround?

 

Share this post


Link to post
Share on other sites

Is there a recommended solution for this issue?

Share this post


Link to post
Share on other sites

I've opened a case with support (312404) to see what we can do to resolve this issue.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...