Skip to main content
Question

Netskope Publisher - Service Restart instead of Publisher Reboot

  • January 21, 2026
  • 3 replies
  • 43 views

EVC_KyleWilliams
Netskope Partner

Hi Community

 

Happy New Year :) 

 

I’m keen to understand if a Publisher Reboot is necessary every time a change is made to the local host file when using it for DNS resolution of applications hosted in Azure?

 

It seems like a Publisher reboot is required when adding in entries?

 

Is there a service that can be restarted instead for the changes to take effect?

 

I’ve had a scrounge through the Community and Documentation pages but haven’t been successful in finding any info.

 

Thanks in advance.

3 replies

notskope
  • New Member III
  • January 27, 2026

Managing individual host files sounds like a nightmare, you can’t use your DNS servers for this?


EVC_KyleWilliams
Netskope Partner

Managing individual host files sounds like a nightmare, you can’t use your DNS servers for this?

Unfortunately not an option for this particular environment :(


Forum|alt.badge.img+16
  • Netskope Employee
  • February 9, 2026

The Publisher container restarting should suffice as the hosts file is loaded into the Publisher at start time.  I don’t have the commands to do so handy at the moment but I don’t believe you need to restart the entire host.