This section discusses NSX Advanced Load Balancer CLI commands and data structures.
The following schema includes the type DNS_RECORD_AAAA
:
[admin:10-10-23-1]: dnspolicy:rule:action> new allow: allow: '(true | false) # Field Type: Optional' reset_conn: '(true | false) # Field Type: Optional' gslb_site_selection: fallback_site_names: <string> is_site_preferred: '(true | false) # Field Type: Optional' site_name: '<string> # Field Type: Optional' pool_switching: pool_group_uuid: '<string> # Field Type: Optional' pool_uuid: '<string> # Field Type: Optional' response: authoritative: '(true | false) # Field Type: Optional' rcode: '<choices: DNS_RCODE_NOERROR | DNS_RCODE_NXDOMAIN | NS_RCODE_YXDOMAIN | DNS_RCODE_REFUSED | DNS_RCODE_FORMERR | DNS_RCODE_YXRRSET | DNS_RCODE_NOTIMP | DNS_RCODE_NOTZONE | DNS_RCODE_SERVFAIL | DNS_RCODE_NXRRSET | DNS_RCODE_NOTAUTH> # Field Type: Optional' resource_record_sets: - resource_record_set: cname: cname: '<string> # Field Type: Required' fqdn: '<string> # Field Type: Optional' ip_addresses: - ip_address: addr: '<string> # Field Type: Required' type: '<choices: V4 | V6 | DNS> # Field Type: Required' nses: - ip_address: addr: '<string> # Field Type: Required' type: '<choices: V4 | V6 | DNS> # Field Type: Required' nsname: '<string> # Field Type: Required' ttl: '<integer> # Field Type: Optional' type: '<choices: DNS_RECORD_DNSKEY | DNS_RECORD_AAAA | DNS_RECORD_A | DNS_RECORD_OTHER | DNS_RECORD_AXFR | DNS_RECORD_SOA | DNS_RECORD_MX | DNS_RECORD_SRV | DNS_RECORD_HINFO | DNS_RECORD_RRSIG | DNS_RECORD_OPT | DNS_RECORD_ANY | DNS_RECORD_PTR | DNS_RECORD_RP | DNS_RECORD_TXT | DNS_RECORD_CNAME | DNS_RECORD_NS> Field Type: Optional' section: '<choices: DNS_MESSAGE_SECTION_QUESTION | DNS_MESSAGE_SECTION_ADDITIONAL | DNS_MESSAGE_SECTION_AUTHORITY | DNS_MESSAGE_SECTION_ANSWER> Field Type: Optional' truncation: '(true | false) # Field Type: Optional' [admin:10-10-23-1]: dnspolicy:rule:action> cancel Exited out of the submode without saving the result.
Processing DNS Request on both SE and Backend Server
A DNS policy needs to be set based on any of the existing match criteria types with match action as either pool or pool group switching so that when a match is found, query will be sent to backend server for response.
For instance, if there is a static record of type A for foo.com on SE, and if a DNS policy is configured stating that if query matches foo.com, action will be pool or pool group switching. In that case you will get response from pool or pool group switched server rather than record present on SE.
Another use case is supporting record types of TXT, NS, and so on, on a server which are not yet supported in GSLB services and redirect those queries to the backend server based on DNS policies.