when booting, a service using UPN logon format cannot start because NETLOGON cannot query the DNS
this was tested on
a Domain Controller server
a server joined to the domain (while DNS was up and running)
11/16 12:55:08 [CRITICAL] [4028] NetpDcGetDcNext: _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.gus.local.: Cannot Query DNS. 1460 0x5b4
if the service is configured with Automatic Start (Delayed Start), it works
if the service is configured with Down-Level logon format, it works
I'd suggest asking the vendor for help or possibly here in their forums.
https://www.wowza.com/community/
--please don't forget to Accept as answer if the reply is helpful--
What service are you asking about?
tried on many, wowza services, 'the-company-i-work-for' services, NSClient service.
DHCP client behaving the same
The DHCP client service should start using the Local Service account
--please don't forget to Accept as answer if the reply is helpful--
correct, i was testing and found out about its dependencies. i was checking that, for example, my MSSQL services don't suffer this issue. can you share any tip to help our devs understand why our services are failing to start at boot when using UPN format?
We wouldn't have any idea. Only the developer knows what happens under the hood with their service so I'd contact support or ask in their forums for help.
--please don't forget to Accept as answer if the reply is helpful--
thanks for your help.
You're welcome.
--please don't forget to Accept as answer if the reply is helpful--
6 people are following this question.
