Azure-docs: Does the Service Fabric DNS Service Overwrite My DNS Settings?

[spottedmahn]

When developing on my local machine using the Service Fabric SDK, I tried changing my obtain DNS server address to auto but it keeps going back: network settings -> adapter settings.

One of my co-workers said that was Service Fabric doing that. I couldn't find anything about this. Is that documented, somewhere?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d273a891-b7f9-81db-bfc5-044e6755541f
• Version Independent ID: dc9f17bb-64af-d4b5-186f-7647c0a0c511
• Content: Azure Service Fabric DNS service
• Content Source: articles/service-fabric/service-fabric-dnsservice.md
• Service: service-fabric
• GitHub Login: @msfussell
• Microsoft Alias: msfussell

[mimckitt]

@spottedmahn Thanks for the feedback! We are currently investigating and will update you shortly.

[mimckitt]

@spottedmahn DNS settings are handled by Azure. Therefore you should not be manually inputting any network settings from inside the VM itself. Rather you should be using the network properties provided to you in the portal. If you make changes inside the VM itself it will often cause you to lose the ability to connect.

[spottedmahn]

Sorry, I left out the critical part. I've updated my question.

When developing on my local machine using the Service Fabric SDK

[mimckitt]

@spottedmahn thanks for clarifying that. Makes more sense now. What version of SF SDK are you using?

[spottedmahn]

3.0.456.9494

[mimckitt]

Thanks for the extra information. @msfussell or @srrengar can either of you shed some light on this question?

[SmegheadSev]

I just upgraded today and had the same issue. Overriding the IPV4 settings from "Obtain DNS Automatically" to "Use the Following" which breaks our internal VPN service that worked with previous versions of the SDK. I'm now using version 3.1.269 which ironically I updated to to get rid of the DNS service warning that was in the SFC explorer. Now the only way I can connect to our company's VPN is to run the local cluster with the DNS service explicitly disabled.

[mimckitt]

@dkkapur would you be able to shed some light on this question?

[mimckitt]

@spottedmahn @SmegheadSev can I have you both please raise this issue to the Service Fabric team directly: https://github.com/Microsoft/service-fabric/issues

Seems it might be am issue with the SDK which they will need to look into and it a bit out of scope for this doc issue.

Please provide a link to the posts when created for tracking purposes. I will close this out as there is no direct action on this specific doc.

[spottedmahn]

Fair enough, thanks @MicahMcKittrick-MSFT.

[mimckitt]

Thanks! I am tracking that issue as well

[spottedmahn]

Hi @MicahMcKittrick-MSFT - as confirmed here: https://github.com/Microsoft/service-fabric/issues/124#issuecomment-389000612, this is intended behavior.

IMO, the docs should reflect the SF behavior. Thoughts?

[v-vasuke]

Docker can also cause this behavior; this isn't necessarily an SF specific issue. Still not a bad idea to include it in the documentation for folks who only run Docker for SF.

[Nickomang]

@spottedmahn, thanks for the feedback. I've added a note in the docs that warns users about the override of DNS settings.

please-close

[spottedmahn]

thanks @Nickomang! any chance you link to the PR or commit? thanks.