-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
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
-
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
-
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
Configure DNS resource records
-
Configure the NetScaler as a forwarder
-
Add a name server
-
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
-
-
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
-
Use source IP address of the client when connecting to the server
-
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 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
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. If you want 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 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>)
or
add dns nameServer ((<IP> | <dnsVserverName>) [-type <type>]
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
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
At the command prompt, type:
add dns nameServer ((<IP> [-local]) | <dnsVserverName>)
Example:
add dns nameServer 10.102.9.19 -local
show dns nameServer
1) 10.102.9.19 LOCAL - State: UP Protocol: UDP
Done
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.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.