NetScaler ingress controller

Configuring wildcard DNS domains through NetScaler Ingress Controller

December 31, 2023

Contributed by:

Wildcard DNS domains are used to handle requests for non-existent domains and subdomains. In a DNS zone, you can use wildcard domains to redirect queries for all non-existent domains or subdomains to a particular server, instead of creating a separate Resource Record (RR) for each domain. The most common use of a wildcard DNS domain is to create a zone that can be used to forward mail from the internet to some other mail system.

For more information on wildcard DNS domains, see the NetScaler documentation.

Now, you can configure wildcard DNS domains on a NetScaler with NetScaler Ingress Controller. Custom Resource Definitions (CRDs) are the primary way of configuring policies in cloud native deployments. Using the Wildcard DNS CRD provided by NetScaler, you can configure wildcard DNS domains on a NetScaler with the NetScaler Ingress Controller. The Wildcard DNS CRD enables communication between NetScaler Ingress Controller and NetScaler for supporting wild card domains.

Usage guidelines and restrictions

For fully qualified domain names (FQDNs), there are multiple ways to add DNS records. You can either enable the NS_CONFIG_DNS_REC variable for NetScaler Ingress Controller for the Ingress resource or use the wildcard DNS CRD. However, you should make sure that they are configured through either CRD or ingress in order to avoid multiple IP mappings to the same domain.
It is recommended to use the Wildcard DNS CRD for the wildcard DNS configurations.
You cannot configure wildcard DNS entries in the DNS address record through ingress if the NS_CONFIG_DNS_REC is enabled for NetScaler Ingress Controller.

Wildcard DNS CRD definition

The Wildcard DNS CRD is available in the NetScaler Ingress Controller GitHub repo at wildcarddnsentry.yaml. The Wildcard DNS CRD provides attributes for the various options that are required to configure wildcard DNS entries on NetScaler.

The following are the attributes provided in the Wildcard DNS CRD:

Attribute	Description
`domain`	Specifies the wild card domain name configured for the zone.
`dnsaddrec`	Specifies the DNS Address record with the IPv4 address of the wildcard domain.
`dnsaaaarec`	Specifies the DNS AAAA record with the IPV6 address of the wildcard domain.
`soarec`	Specifies the SOA record configuration details.
`nsrec`	Specifies the name server configuration details.

Deploy the Wildcard DNS CRD

Perform the following to deploy the Wildcard DNS CRD:

Download the Wildcard DNS CRD.
Deploy the Wildcard DNS CD using the following command:
```
kubectl create -f wildcarddnsentry.yaml
```

How to write a Wildcard DNS configuration policy

After you have deployed the Wildcard DNS CRD provided by NetScaler in the Kubernetes cluster, you can define the wildcard DNS related configuration in a yaml file. In the .yaml file, use wildcarddnsentry in the kind field and in the spec section add the Wildcard DNS CRD attributes based on your requirement for the policy configuration.

The following is a sample YAML file definition that configures a SOA record, NS record, DNS zone, and address and AAAA Records on NetScaler.

apiVersion:
citrix.com/v1
kind: wildcarddnsentry
metadata:
  name: sample-config
spec:
  zone:
    domain: configexample
    dnsaddrec:
      domain-ip: 1.1.1.1
      ttl: 3600
    dnsaaaarec:
      domain-ip: '2001::.1'
      ttl: 3600
    soarec:
      origin-server: n2.configexample.com
      contact: admin.configexample.com
      serial: 100
      refresh: 3600
      retry: 3
      expire: 3600
    nsrec:
      nameserver: n1.configexample.com
      ttl: 3600
<!--NeedCopy-->

After you have defined the DNS configuration, deploy the wildcarddns-example.yaml file using the following command.

     kubectl create -f wildcarddns-example.yaml

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Configuring wildcard DNS domains through NetScaler Ingress Controller

December 31, 2023

Contributed by:

December 31, 2023

Contributed by:

Configuring wildcard DNS domains through NetScaler Ingress Controller

Usage guidelines and restrictions

Wildcard DNS CRD definition

Deploy the Wildcard DNS CRD

How to write a Wildcard DNS configuration policy

In this article