Tranquil IT Forum

Hello,

when I install WAPT server on a Debian 9 machine, I have no problems until I try to configure Kerberos.

The "kinit" command always returns the following error:
Cannot contact any KDC for realm 'MONDOMAINE.LOCAL' while getting initial credentials

. The server name is correctly resolved at the DNS level.

The AD server (and Kerberos) is running Windows Server 2016.
The WAPT version is 1.5.23.

Well, after searching for quite a while, it seems the ".LOCAL" extension simply doesn't work.
I just tested it with the ".INTRA" extension and I no longer have any problems.

Hello Nicoge,

Nicoge wrote: ↑Apr 16, 2018 - 2:58 PM Well, after searching for quite a while, it seems that the ".LOCAL" extension simply doesn't work.
I just tested it with the ".INTRA" extension and I no longer have any problems.

It can work with a .LOCAL.

The problem with .local comes from the Bonjour/MDNS protocol (multicast DNS). One day, a few years ago, Apple decreed that the .local suffix would correspond to DNS names resolvable via multicast (a bit like NetBIOS broadcast) with its Bonjour protocol.

So now we can no longer use this suffix unless we disable mdns, and that's that. On most Linux distributions, mdns is now configured by default (see the /etc/nsswitch.conf file). On Windows, it's enabled when you install certain programs like Adobe Photoshop. On Macs, it's always installed.

So basically, if you have a new domain to set up, don't use the .local suffix.

Denis

Thank you for this explanation.

As it was a test domain, I will stick with the .intra for now, but I know how to react now in case of problems with the .local!