search

microsoft / service-fabric

Service Fabric is a distributed systems platform for packaging, deploying, and managing stateless and stateful distributed applications and containers at large scale.
https://docs.microsoft.com/en-us/azure/service-fabric/
MIT License
3.01k stars 399 forks source link

DNS service returns "No such host is known." #1090

Open mcurko opened 3 years ago

mcurko commented 3 years ago

Service Fabric Runtime Version: 7.1.458.9590

Environment: Dev cluster

Description: This example doesn't work on Dev cluster but works on standalone one-node windows cluster. In both situations DnsService is present in the cluster. Following the information on https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-dnsservice, a project is created and attached to this issue. It consists of 2 stateless web APIs, one calling another ("front" -> "back") via internal DNS resolution. On Dev cluster it fails with message "No such host is known."

On both clusters the "back" controller can be reached by: http://localhost:7002/weatherforecast http://localhost:19081/myapp/back/weatherforecast but only on standalone server by http://localhost:7001/weatherforecast

myapp.zip

Observed behavior: error "No such host is known."

Expected Behavior: the same as on the standalone cluster

OS(Windows/Linux): Windows

If this is a regression, which version did it regress from? n/a

Assignees: /cc @microsoft/service-fabric-triage

craftyhouse commented 3 years ago

Still facing this problem or were you able to resolve?

Dev cluster is running where? Azure?

mcurko commented 3 years ago

Well, I don't have the solution to the problem at all.

craftyhouse commented 3 years ago

Where is the "dev" cluster running? If it's on azure did you enable reverse proxy in deployment? Might be the issue? I'll see if I have time to repro using azure

mcurko commented 3 years ago

By Dev cluster I mean the development 1/5-node cluster installed on my development machine.

ordinaryorange commented 10 months ago

Is there any progress on the DNS issues ? Stood up a Dev cluster on my local machine, and another in a fresh VM on Azure to confirm. All the below is common. Created a basic stateless service from the Visual Studio 2022 template. Added ServiceDnsName="Stateless1" to the startup services xml. Ran the project to push the service into SF.