Page 1 of 2
macOS: problem reported, machine name
Published: November 18, 2025 - 2:46 PM
by Clafon
WAPT Version: 2.6.1.17567
Server OS: Debian 12
Administration Machine OS: Windows Server 2022
Target OS: macOS 26.0 and 14.5
Hello,
since installing the new version, in the administration console some of our Macs are showing up with a name in the format "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" while others are not (same OS).
Each Mac has a hostname in the format "macXX.local".
Have you encountered this issue before?
Thank you
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:13 PM
by sfonteneau
Hello,
is the Mac on the domain?
Does a /etc/krb5.keytab file exist?
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:20 PM
by Clafon
Hello Simone,
no, the Macs are not domain-bound and the /etc/krb5.keytab file is indeed present.
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:28 PM
by sfonteneau
On a Mac, it would be interesting to do a:
Code: Select all
wapt-get shell
>>> from setuphelpers import *
>>> get_hostname_and_domain()
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:31 PM
by sfonteneau
I think you'll end up here in any case:
Who performs an IP-to-name resolution to obtain a fully qualified domain name (FQDN)?
We would need to change that in wapt but it's more of a headache than it seems.
In your case, logically you should retrieve only the hostname, but without the domain.
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:37 PM
by Clafon
sfonteneau wrote: ↑Nov 18, 2025 - 3:28 PM
On a Mac, it would be interesting to do a:
Code: Select all
wapt-get shell
>>> from setuphelpers import *
>>> get_hostname_and_domain()
I placed the orders but received an error message:
Traceback (most recent call last):
File "<console> ", line 1, in<module>
NameError: name 'get_hostname_and_domain' is not defined
Re: macOS: problem reported machine name
Published: November 18, 2025 - 3:37 PM
by Clafon
sfonteneau wrote: ↑Nov 18, 2025 - 3:31 PM
In your case, logically you should retrieve only the hostname, but without the domain
So I would need to remove ".local" from the hostname?
Re: macOS: problem reported machine name
Published: November 19, 2025 - 2:04 PM
by sfonteneau
Just try doing this:
`import socket
socket.getfqdn()
` to verify the theory
Re: macOS: problem reported machine name
Published: November 19, 2025 - 5:22 PM
by Clafon
Good evening,
here is the output when running the command:
wapt-get shell
import socket
socket.getfqdn()
'1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa'
Re: macOS: problem reported machine name
Published: November 20, 2025 - 09:16
by sfonteneau
So that's right,
it's the socket library integrated into Python that's communicating, see:
https://docs.python.org/3/library/socke ... et.getfqdn.
Here it's the reverse IP address resolution that's working...
try putting a "." in the hostname to see if that works, but I doubt it will.
Simon