How to Configure a DNS View for Global Server Load Balancing on a NetScaler Appliance
Article ID: CTX127590
Updated On:
Description
This article contains information about configuring a DNS view for Global Server Load Balancing on a NetScaler appliance.
Background
Based on the parameters that identify the client requests, you can use DNS views to control IP address returned in a DNS query. For example, you can use DNS views to control the client requests based in the source of the request. If the request is from a client within the LAN, then return a specific IP address. However, if the request is from a client from another network, then return another IP address.
You can configure DNS views to support only Global Server Load Balancing records. DNS views also support DNS proxy and ADNS deployments.
You must configure DNS policies on the NetScaler appliance to verify if a DNS view is applied. Consider the following points when configuring a DNS policy:
-
DNS policies are verified every time a client connection is made.
-
DNS policy should verify the condition applied to the connection. For example, if the client IP is in range 10.10.0.0/24, then apply a DNS view.
-
DNS policy must be bound globally.
-
You can apply priorities to the DNS policies. This influences the order of policy processing.
-
If a policy applies a view, then the statement returns the configured value.
Instructions
To configure a DNS view for Global Server Load Balancing on a NetScaler appliance complete the following steps:
-
Run the following command to add a DNS view:
> add dns view <View_Name> -
Run the following command to bind a Global Server Load Balancing service to the DNS view you created:
> bind gslb service <Service_Name> –view <View_Name> <IP_Address> -
Run the following command to add a DNS policy:
> add dns policy <Policy_Name> “<Rule>” –viewName <View_Name>The following are two sample DNS policies for your reference:
In the preceding samples, the Test1 policy verifies if the client request is received from the subnet 10.10.0.0/16 and if the request is from this subnet, then the Internal DNS view is applied and the IP address configured for the view is returned to the client. Similarly, the Test2 policy verifies if the request is received from the interface with a specific MAC address and returns the IP address configured for the corresponding DNS view.
add dns policy Test1 “CLIENT.IP.SRC.IN_SUBNET(10.10.0.0/16)” –viewName Internal
add dns policy Test2 “CLIENT.ETHER.SRCMAC.EQ(00:0f:b5:fe:a2:13)” –viewName Internal -
Run the following command to bind the DNS view globally:
> bind dns global <View_Name> <Priority>
Warning: When applying a DNS View, the Client Request will only be able to resolve GSLB services with that DNS View bound, it will not be able to resolve GSLB services with no DNS View bound
You must bind the View to all GSLB services, that you want the Client to resolve
Issue/Introduction
