You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-dnsservice.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ ms.date: 07/14/2022
12
12
# DNS service in Azure Service Fabric
13
13
DNS service is an optional system service that you can enable in your cluster to discover other services using the DNS protocol.
14
14
15
-
Many services, especially containerized services, are addressable through a pre-existing URL. Being able to resolve these services using the standard DNS protocol, rather than the Service Fabric Naming Service protocol, is desirable. DNS service enables you to map DNS names to a service name and hence resolve endpoint IP addresses. Such functionality maintains the portability of containerized services across different platforms and can make "lift and shift" scenarios easier, by letting you use existing service URLs rather rewriting code to use the Naming Service.
15
+
Many services, especially containerized services, are addressable through a pre-existing URL. Being able to resolve these services using the standard DNS protocol, rather than the Service Fabric Naming Service protocol, is desirable. DNS service enables you to map DNS names to a service name and hence resolve endpoint IP addresses. Such functionality maintains the portability of containerized services across different platforms and can make "lift and shift" scenarios easier, by letting you use existing service URLs rather than rewriting code to use the Naming Service.
16
16
17
17
DNS service maps DNS names to service names, which in turn are resolved by the Naming Service to return the service endpoint. The DNS name for the service is provided at the time of creation. The following diagram shows how DNS service works for stateless services. For brevity, the diagrams only show one endpoint for the services, although each service can have multiple endpoints.
18
18
19
-
19
+
20
20
21
21
Beginning with Service Fabric version 6.3, the Service Fabric DNS protocol has been extended to include a scheme for addressing partitioned stateful services. These extensions make it possible to resolve specific partition IP addresses using a combination of stateful service DNS name and the partition name. All three partitioning schemes are supported:
22
22
@@ -26,7 +26,7 @@ Beginning with Service Fabric version 6.3, the Service Fabric DNS protocol has b
26
26
27
27
The following diagram shows how DNS service works for partitioned stateful services.
28
28
29
-
29
+
30
30
31
31
For more information on partitioned queries, refer to the [section below](#making-dns-queries-on-a-stateful-service-partition).
32
32
@@ -44,11 +44,11 @@ To deploy a new cluster with ARM templates, you can either use the [sample templ
44
44
#### Clusters using Azure portal
45
45
If you are creating a standard cluster in the portal, DNS service is enabled by default in the **Include DNS service** option under the **Add on features** section.
46
46
47
-
47
+
48
48
49
49
If you are creating a managed cluster in the portal, DNS service is enabled by default in the **DNS service** option under the **Add on features** section.
50
50
51
-
51
+
52
52
53
53
### Existing clusters
54
54
If you are updating an existing managed cluster to enable DNS service, you can do so from the portal by visiting the **Add-on services** page from the cluster resource page. Otherwise, you can enable DNS service using alternative methods that are referenced below:
@@ -239,7 +239,7 @@ Update-ServiceFabricService `
239
239
### Verify that a DNS name is set in Service Fabric Explorer
240
240
Once the service is deployed with the DNS name, Service Fabric Explorer will show the DNS name for the service, as shown in the following figure:
241
241
242
-
242
+
243
243
244
244
> [!NOTE]
245
245
> This view may be different depending on the version of Service Fabric Explorer used, however, the DNS name field should be visible in some form on the service page.
@@ -337,11 +337,11 @@ public class ValuesController : Controller
337
337
## Recursive queries
338
338
For DNS names that DNS service can't resolve on its own (for example, a public DNS name), it will forward the query to pre-existing recursive DNS servers on the nodes.
339
339
340
-
340
+
341
341
342
342
Prior to Service Fabric 9.0, these servers were queried serially until a response was received, with a fixed timeout period of 5 seconds in between. If a server didn't respond within the timeout period, the next server (if available) would be queried. In the case that these DNS servers were encountering any issues, completion of DNS queries would take longer than 5 seconds, which is not ideal.
343
343
344
-
Beginning in Service Fabric 9.0, support for parallel recursive queries was added. With parallel queries, all recursive DNS servers can be contacted at once, where the first response wins. This results in quicker responses in the scenario previously mentioned. This option is not enabled by default, although this may change in a future update.
344
+
Beginning in Service Fabric 9.0, support for parallel recursive queries was added. With parallel queries, all recursive DNS servers can be contacted at once, where the first response wins. This results in quicker responses in the scenario previously mentioned. This option is not enabled by default.
345
345
346
346
Fine-grained options are also introduced in Service Fabric 9.0 to control the behavior of the recursive queries, including the timeout periods and query attempts. These options can be set in the [DNS service settings](./service-fabric-cluster-fabric-settings.md#dnsservice):
0 commit comments