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/avere-vfxt/avere-vfxt-configure-dns.md
+33-28Lines changed: 33 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Configuring a DNS server for round-robin load balancing with Avere
4
4
author: ekpgh
5
5
ms.service: avere-vfxt
6
6
ms.topic: conceptual
7
-
ms.date: 12/19/2019
7
+
ms.date: 10/07/2021
8
8
ms.author: rohogue
9
9
---
10
10
@@ -30,42 +30,47 @@ To distribute the overall load, configure your DNS domain to use round-robin loa
30
30
31
31
## Configuration details
32
32
33
-
When clients access the cluster, RRDNS automatically balances their requests among all available interfaces.
33
+
When clients access the cluster, round-robin DNS (RRDNS) automatically balances their requests among all available interfaces.
34
34
35
-
For optimal performance, configure your DNS serverto handle client-facing cluster addresses as shown in the following diagram.
35
+
To set this system up, you need to customize the DNS server's configuration file so that when it gets mount requests to the vFXT cluster's main domain address, it assigns the traffic among all of the vFXT cluster's mount points. Clients mount the vFXT cluster using its domain name as the server argument, and are routed to the next mount IP automatically.
36
36
37
-
A cluster vserver is shown on the left, and IP addresses appear in the center and on the right. Configure each client access point with A records and pointers as illustrated.
37
+
There are two main steps to configure RRDNS:
38
38
39
-
40
-
<!--- separate text description file provided [diagram text description](avere-vfxt-rrdns-alt-text.md) -->
39
+
1. Modify your DNS server’s ``named.conf`` file to set cyclic order for queries to your vFXT cluster. This option causes the server to cycle through all of the available IP values. Add a statement like the following:
41
40
42
-
Each client-facing IP address must have a unique name for internal use by the cluster. (In this diagram, the client IPs are named vs1-client-IP-* for clarity, but in production you should probably use something more concise, like client*.)
41
+
```bash
42
+
options {
43
+
rrset-order {
44
+
class IN A name "vfxt.contoso.com" order cyclic;
45
+
};
46
+
};
47
+
```
43
48
44
-
Clients mount the cluster using the vserver name as the server argument.
49
+
1. Configure A records and pointer (PTR) records for each available IP address as in the following example.
45
50
46
-
Modify your DNS server’s``named.conf``file to set cyclic order for queries to your vserver. This option ensures that all of the available values are cycled through. Add a statement like the following:
51
+
These``nsupdate``commands provide an example of configuring DNS correctly for a vFXT cluster with the domain name vfxt.contoso.com and three mount addresses (10.0.0.10, 10.0.0.11, and 10.0.0.12):
47
52
48
-
```
49
-
options {
50
-
rrset-order {
51
-
class IN A name "vserver1.example.com" order cyclic;
52
-
};
53
-
};
54
-
```
53
+
```bash
54
+
update add vfxt.contoso.com. 86400 A 10.0.0.10
55
+
update add vfxt.contoso.com. 86400 A 10.0.0.11
56
+
update add vfxt.contoso.com. 86400 A 10.0.0.12
57
+
update add client-IP-10.contoso.com. 86400 A 10.0.0.10
58
+
update add client-IP-11.contoso.com. 86400 A 10.0.0.11
59
+
update add client-IP-12.contoso.com. 86400 A 10.0.0.12
The following ``nsupdate``commands provide an example of configuring DNS correctly:
65
+
These commands create an A record for each of the cluster's mount addresses, and also set up pointer records to support reverse DNS checks appropriately.
57
66
58
-
```
59
-
update add vserver1.example.com. 86400 A 10.0.0.10
60
-
update add vserver1.example.com. 86400 A 10.0.0.11
61
-
update add vserver1.example.com. 86400 A 10.0.0.12
62
-
update add vs1-client-IP-10.example.com. 86400 A 10.0.0.10
63
-
update add vs1-client-IP-11.example.com. 86400 A 10.0.0.11
64
-
update add vs1-client-IP-12.example.com. 86400 A 10.0.0.12
The diagram below shows the basic structure of this configuration.
68
+
69
+
:::image type="complex" source="media/round-robin-dns-diagram-vfxt.png" alt-text="Diagram showing client mount point DNS configuration.":::
70
+
<The diagram shows connections among three categories of elements: the single vFXT cluster domain name (at the left), three IP addresses (middle column), and three internal-use reverse DNS client interfaces (right column). A single oval at the left labeled "vfxt.contoso.com" is connected by arrows pointing toward three ovals labeled with IP addresses: 10.0.0.10, 10.0.0.11, and 10.0.0.12. The arrows from the vfxt.contoso.com oval to the three IP ovals are labeled "A". Each of the IP address ovals is connected by two arrows to an oval labeled as a client interface - the oval with IP 10.0.0.10 is connected to "client-IP-10.contoso.com", the oval with IP 10.0.0.11 is connected to "client-IP-11.contoso.com", and the oval with IP 10.0.0.12 is connected to "client-IP-11.contoso.com". The connections between the IP address ovals and the client interface ovals are two arrows: one arrow labeled "PTR" that points from the IP address oval to the client interface oval, and one arrow labeled "A" that points from the client interface oval to the IP address oval.>
71
+
:::image-end:::
72
+
73
+
After the RRDNS system is configured, tell your client machines to use it to resolve the cluster address in their mount commands.
Copy file name to clipboardExpand all lines: articles/fxt-edge-filer/configure-network.md
+37-33Lines changed: 37 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ekpgh
5
5
ms.author: v-erkel
6
6
ms.service: fxt-edge-filer
7
7
ms.topic: tutorial
8
-
ms.date: 06/20/2019
8
+
ms.date: 10/07/2021
9
9
---
10
10
11
11
# Tutorial: Configure the cluster's network settings
@@ -97,43 +97,47 @@ Keep these things in mind when deciding whether or not to use a DNS server:
97
97
98
98
### Round-robin DNS configuration details
99
99
100
-
When clients access the cluster, RRDNSautomatically balances their requests among all available interfaces.
100
+
A round-robin DNS (RRDNS) system automatically routes client requests among multiple addresses.
101
101
102
-
For optimal performance, configure your DNS serverto handle client-facing cluster addresses as shown in the following diagram.
102
+
To set this system up, you need to customize the DNS server's configuration file so that when it gets mount requests to the FXT Edge Filer's main domain address, it assigns the traffic among all of the cluster's mount points. Clients mount the cluster using its domain name as the server argument, and are routed to the next mount IP automatically.
103
103
104
-
A cluster vserver is shown on the left, and IP addresses appear in the center and on the right. Configure each client access point with A records and pointers as illustrated.
104
+
There are two main steps to configure RRDNS:
105
105
106
-
:::image type="complex" source="media/fxt-cluster-config/fxt-rrdns-diagram.png" alt-text="Diagram showing cluster round-robin DNS configuration.":::
107
-
<The diagram shows connections among three categories of elements: a single vserver (at the left), three IP addresses (middle column), and three client interfaces (right column). A single circle at the left labeled "vserver1" is connected by arrows pointing toward three circles labeled with IP addresses: 10.0.0.10, 10.0.0.11, and 10.0.0.12. The arrows from the vserver circle to the three IP circles have the caption "A". Each of the IP address circles is connected by two arrows to a circle labeled as a client interface - the circle with IP 10.0.0.10 is connected to "vs1-client-IP-10", the circle with IP 10.0.0.11 is connected to "vs1-client-IP-11", and the circle with IP 10.0.0.12 is connected to "vs1-client-IP-11". The connections between the IP address circles and the client interface circles are two arrows: one arrow labeled "PTR" that points from the IP address circle to the client interface circle, and one arrow labeled "A" that points from the client interface circle to the IP address circle.>
106
+
1. Modify your DNS server’s ``named.conf`` file to set cyclic order for queries to your FXT cluster. This option causes the server to cycle through all of the available IP values. Add a statement like the following:
107
+
108
+
```bash
109
+
options {
110
+
rrset-order {
111
+
class IN A name "fxt.contoso.com" order cyclic;
112
+
};
113
+
};
114
+
```
115
+
116
+
1. Configure A records and pointer (PTR) records for each available IP address as in the following example.
117
+
118
+
These ``nsupdate`` commands provide an example of configuring DNS correctly for an Azure FXT Edge Filer cluster with the domain name fxt.contoso.com and three mount addresses (10.0.0.10, 10.0.0.11, and 10.0.0.12):
119
+
120
+
```bash
121
+
update add fxt.contoso.com. 86400 A 10.0.0.10
122
+
update add fxt.contoso.com. 86400 A 10.0.0.11
123
+
update add fxt.contoso.com. 86400 A 10.0.0.12
124
+
update add client-IP-10.contoso.com. 86400 A 10.0.0.10
125
+
update add client-IP-11.contoso.com. 86400 A 10.0.0.11
126
+
update add client-IP-12.contoso.com. 86400 A 10.0.0.12
These commands create an A record for each of the cluster's mount addresses, and also set up pointer records to support reverse DNS checks appropriately.
133
+
134
+
The diagram below shows the basic structure of this configuration.
135
+
136
+
:::image type="complex" source="media/round-robin-dns-diagram-fxt.png" alt-text="Diagram showing client mount point DNS configuration.":::
137
+
<The diagram shows connections among three categories of elements: the single FXT Edge Filer cluster domain name (at the left), three IP addresses (middle column), and three internal-use reverse DNS client interfaces (right column). A single oval at the left labeled "fxt.contoso.com" is connected by arrows pointing toward three ovals labeled with IP addresses: 10.0.0.10, 10.0.0.11, and 10.0.0.12. The arrows from the fxt.contoso.com oval to the three IP ovals are labeled "A". Each of the IP address ovals is connected by two arrows to an oval labeled as a client interface - the oval with IP 10.0.0.10 is connected to "client-IP-10.contoso.com", the oval with IP 10.0.0.11 is connected to "client-IP-11.contoso.com", and the oval with IP 10.0.0.12 is connected to "client-IP-11.contoso.com". The connections between the IP address ovals and the client interface ovals are two arrows: one arrow labeled "PTR" that points from the IP address oval to the client interface oval, and one arrow labeled "A" that points from the client interface oval to the IP address oval.>
108
138
:::image-end:::
109
139
110
-
Each client-facing IP address must have a unique name for internal use by the cluster. (In this diagram, the client IPs are named vs1-client-IP-* for clarity, but in production you should probably use something more concise, like client*.)
111
-
112
-
Clients mount the cluster using the vserver name as the server argument.
113
-
114
-
Modify your DNS server’s ``named.conf`` file to set cyclic order for queries to your vserver. This option ensures that all of the available values are cycled through. Add a statement like the following:
115
-
116
-
```
117
-
options {
118
-
rrset-order {
119
-
class IN A name "vserver1.example.com" order cyclic;
120
-
};
121
-
};
122
-
```
123
-
124
-
The following ``nsupdate`` commands provide an example of configuring DNS correctly:
125
-
126
-
```
127
-
update add vserver1.example.com. 86400 A 10.0.0.10
128
-
update add vserver1.example.com. 86400 A 10.0.0.11
129
-
update add vserver1.example.com. 86400 A 10.0.0.12
130
-
update add vs1-client-IP-10.example.com. 86400 A 10.0.0.10
131
-
update add vs1-client-IP-11.example.com. 86400 A 10.0.0.11
132
-
update add vs1-client-IP-12.example.com. 86400 A 10.0.0.12
0 commit comments