| Note | ||
|---|---|---|
| ||
From NIOS-9.x release, IB-4030 and IB-4030-10GE appliances are not supported. |
You now have the ability to switch between BIND or Unbound resolvers on IB-4030-10GE appliances. Following are a couple scenarios for which you may consider using Unbound DNS resolution:
...
| Unsupported features | Notes |
|---|---|
| Authoritative name server and all related functions | Unsupported features include but are not limited to DNS64, AAAA filtering, DDNS updates, notify source and delay, wildcard, bulk hosts, IP blocks/IP block groups, and DNS zone transfers. Unbound DNS supports forward and stub zones. |
| Security related features | Some security related features are not supported. They include the following: DNS blackhole lists, DNS blacklist rulesets, GSS-TSIG, enabling and disabling accept-expired-signature for DNSSEC (other aspects of DNSSEC are supported, such as trust anchors and negative trust anchors), NXDOMAIN mitigation/RRL (Response Rate Limiting), recursive client limits, recursive client SNMP traps, and Infoblox DNS Firewall (RPZ). Note: The TSIG Key menu item remains in the Queries and Recursive Queries tables even though it is not supported for Unbound DNS. |
| UDP source port configuration | Port configuration and network settings are automatically switched between Unbound DNS and standard DNS when you change the DNS resolution configuration. |
| DNS requests through a single TCP session | This is not supported for Unbound DNS even though this option might appear in the Member Security Properties editor of the Grid Manager when Unbound is configured for the member. |
| DNS views | User-defined DNS views are not supported. Unbound DNS supports only the default DNS view. |
| Logging | DNS query logging and DNS response logging are not supported. Logging format and severity levels for Unbound DNS are different than that of the standard DNS. For more information, see Unbound DNS Logging above. |
| Reporting | The DNS Replies Trend report is the only supported report for Unbound DNS. Also, the DNS Response Latency Trend report periodically queries against the DNS server to determine latency and is not affected by Unbound DNS. All other reports that do not support Unbound are still available and include data from members running standard DNS. However, they do not collect data from members using Unbound DNS. For information about reports for IB-4030-10GE, see Reports for IB-4030 and IB-4030-10GEDNS Statistics for Cache Acceleration. |
| RRset order | This is not supported. For information about this feature, see Preserving the RRset Order for Cached DNS ResponsesManaging Query Performance. |
| Sort list | This is not supported. For information about this feature, see Defining Sort List for Cached DNS Responses. |
| HSM group status and traps | Although HSM groups are not supported, the HSM event type remains visible in the Notifications tab of the Grid Member Properties editor. |
| Other DNS features | The following DNS enhancements are not supported: DNS query capture, disabling EDNS0 (Extension Mechanism for DNS), DNS Traffic Control, HA mode transition optimizations, and DNS fault tolerant caching. |
...