本节介绍了 NSX Advanced Load Balancer CLI 命令和数据结构。
注:
以下架构包括 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.
在 SE 和后端服务器上处理 DNS 请求
需要根据任何现有的匹配条件类型设置 DNS 策略,并将池或池组切换作为匹配操作,以便在找到匹配项时,将查询发送到后端服务器以获取响应。
例如,在 SE 上具有 foo.com 的 A 类型静态记录,并且配置了 DNS 策略,以指出如果查询与 foo.com 匹配,则操作为池或池组切换。在这种情况下,您将从池或池组切换的服务器获得响应,而不是 SE 上存在的记录。
另一个用例是,在服务器上支持 TXT、NS 等记录类型,但在 GSLB 服务中还不支持这些记录类型,并根据 DNS 策略将这些查询重定向到后端服务器。