On Premise Service Fabric - Cannot change DNS settings, values revert on a reboot

Richard Fennell 7 Reputation points MVP

I have a client who is running a number of on premises Service Fabric clusters, each hosting a number of services.

As part of a general network upgrade, they are changing their network's DNS servers to new VMs (hence IP addresses).

They have manually changed the static DNS entries on the nodes in their Service Fabric clusters. However, when a node is rebooted it reverts back to their original settings.

Note that the Service Fabric DNS service is enabled on the clusters. So the first DNS entry on each node is the node itself followed by the 3 local network DNS servers that are statically set on the LAN adaptor. It is these 3 values that are being changed.

The question is does Service Fabric somehow cache the DNS entries? And if so can this be refreshed/updated?

Note that the Service Fabric clusters are not yet patched to the latest version, 7.0. So has there been any bug in this area in previous versions?

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
253 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Richard Fennell 7 Reputation points MVP

    An update and answer ...

    As we were on a not currently supported version of Service Fabric (it was 6.1.x on one cluster and 6.4.x on another) we upgraded to 7.0.x.

    Once this was done the DNS values persisted when a node was rebooted

    1 person found this answer helpful.

  2. KarishmaTiwari-MSFT 18,657 Reputation points Microsoft Employee

    Can you please share which service fabric version are you using?

    In order to check for any bugs and bug fixes in any version, please check the release notes for that version here:

    0 comments No comments