This is a bit of a weird one. I'm building a new web server hosted on a LAMP stack to replace an old IIS server. Its intended DNS name is currently occupied by the old server. I have SSL certificates set up for the new server, and configs ready to move the DNS over, but I'd like to have an SPN/TGT (HTTP/{fqdn}@{domain}) set up on the host in advance as well. I can have a separate service account to maintain it, problem is the FQDN is currently occupied.
Will creating that SPN on the LAMP host rob the IIS host of the ability to authenticate users through kerberos?