-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Configure DNS resource records
-
Configure the NetScaler as a forwarder
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configure the NetScaler appliance as a forwarder
A forwarder is a server that forwards DNS queries to DNS servers that are outside the forwarder server’s network. Queries that cannot be resolved locally are forwarded to other DNS servers. A forwarder accumulates external DNS information in its cache as it resolves DNS queries. To configure the NetScaler appliance as a forwarder, you must add an external name server.
The NetScaler appliance allows you to add external name servers to which it can forward the name resolution queries that cannot be resolved locally. To configure the NetScaler appliance as a forwarder, you must add the name servers to which it must forward name resolution queries. You can specify the lookup priority to specify the name service that the NetScaler appliance must use for name resolution.
For information on how to configure the NetScaler appliance as a forwarder, see Add a name server (when the NetScaler appliance acts as a forwarder) by using the CLI.
Note:
The NetScaler appliance in forwarder mode supports TCP, UDP, and UDP-TCP name servers.
- If you have configured a TCP name server, then the NetScaler appliance sends the DNS request over TCP.
- If you have configured a UDP name server, then the NetScaler appliance sends the DNS request over UDP.
- If you have configured a UDP-TCP name server, then the NetScaler appliance sends the DNS request over UDP. However if the truncated bit is set in the DNS response, the appliance sends such DNS requests over TCP.
Add a name server
You can create a name server by specifying its IP address or by configuring an existing virtual server as the name server.
- IP address-based name server - An external name server to contact for domain name resolution. If multiple IP address-based name servers are configured on the appliance, and the local parameter is not set on any of them, incoming DNS queries are load balanced across all the name servers, in round robin fashion.
- Virtual server-based name server - A DNS virtual server configured in the NetScaler. For more fine-grained control on how external DNS name servers are load balanced (for example, you want a load balancing method other than round robin), do the following:
- Configure a DNS virtual server on the appliance
- Bind the external name servers as its services
- Specify the name of the virtual server in this command.
To verify the configuration, you can use the show dns nameServer
command.
To remove a name server, at the NetScaler CLI, type the rm dns nameServer
command followed by the IP address of the name server.
To view the details of the DNS nameserver, at the NetScaler CLI, type the show dns nameServer
command followed by the IP address of the name server.
Add a name server (when the NetScaler appliance acts as a forwarder) by using the CLI
At the command prompt, type;
add dns nameServer ((<IP>) | <dnsVserverName>)
<!--NeedCopy-->
Or
add dns nameServer ((<IP> | <dnsVserverName>) [-type <type>]
<!--NeedCopy-->
Examples:
add dns nameServer dnsVirtualNS
add dns nameServer 192.0.2.11 -type TCP
add dns nameServer 192.0.2.12 -type UDP_TCP
add dns nameServer 192.0.2.10
show dns nameServer 192.0.2.10
1) 192.0.2.10 - State: UP Protocol: UDP
Done
<!--NeedCopy-->
Note:
If the name server type is not specified, a UDP name server is created by default. To create a name server of type TCP or UDP_TCP, you must specify the type.
When you specify the type as UDP_TCP, two name servers (one UDP name server and one TCP name server) are created for the given IP address.
Add a name server (when the NetScaler appliance acts as a resolver) by using the CLI
Specify the local
parameter for a recursive resolver. Enable recursion using the set dns parameter
command.
At the command prompt, type:
add dns nameServer ((<IP> [-local]) | <dnsVserverName>)
show dns nameServer
set dns parameter -recursion ENABLED
show dns parameter
<!--NeedCopy-->
Example:
add dns nameServer 10.102.9.19 -local
show dns nameServer
1) 10.102.9.19 LOCAL - State: UP Protocol: UDP
Done
set dns parameter -recursion ENABLED
Done
show dns parameter
DNS parameters:
.
.
.
Recursive Resolution : ENABLED
.
.
.
Done
<!--NeedCopy-->
Local - Mark the IP address as one that belongs to a local recursive DNS server on the NetScaler appliance. The appliance recursively resolves queries received on an IP address that is marked as being local.
For recursive resolution to work, the global DNS parameter, recursion
, must also be set.
If no name server is marked as being local, the appliance functions as a stub resolver and load balances the name servers.
Add a name server by using the GUI
Navigate to Traffic Management > DNS > Name Servers and create a name server.
Set DNS lookup priority
You can set the lookup priority to either DNS or WINS. This option is used in the SSL VPN mode of operation.
Set the lookup priority to DNS by using the CLI
At the command prompt, type the following commands to set the lookup priority to DNS and verify the configuration:
- set dns parameter -nameLookupPriority (DNS | WINS)
- show dns parameter
<!--NeedCopy-->
Example:
> set dns parameter -nameLookupPriority DNS
Done
> show dns parameter
.
.
.
Name lookup priority : DNS
.
.
.
Done
<!--NeedCopy-->
Set lookup priority to DNS by using the GUI
- Navigate to Traffic Management > DNS.
- In the details pane, under Settings, click Change DNS settings.
- In the Configure DNS Parameters dialog box, under Name Lookup Priority, select DNS or WINS, and then click OK.
Note
If the DNS virtual server that you have configured is DOWN and if you set the
-nameLookupPriority
to DNS, the NetScaler does not attempt WINS lookup. Therefore, if a DNS virtual server is not configured or is disabled, set the-nameLookupPriority
to WINS.
Disable and enable name servers
The following procedure describes the steps to enable or disable an existing name server.
Enable or disable a name server by using the CLI
At the command prompt, type the following commands to enable or disable a name server and verify the configuration:
- (enable | disable) dns nameServer <IPAddress>
- show dns nameServer <IPAddress>
<!--NeedCopy-->
Example:
> disable dns nameServer 10.102.9.19
Done
> show dns nameServer 10.102.9.19
1) 10.102.9.19: LOCAL - State: OUT OF SERVICE
Done
<!--NeedCopy-->
Enable or disable a name server by using the GUI
- Navigate to Traffic Management > DNS > Name Servers.
- In the details pane, select the name server that you want to enable or disable.
- Click Enable or Disable. If a name server is enabled, the Disable option is available. If a name server is disabled, the Enable option is available.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.