| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| infoblox_nios:dns [2025/12/09 13:18] – [External DNS] bstafford | infoblox_nios:dns [2025/12/18 11:00] (current) – [External DNS] bstafford |
|---|
| |
| Or you can make the NIOS entries in the Name Server Group to be "Stealth" and then add the external IP addresses as External Secondaries. | Or you can make the NIOS entries in the Name Server Group to be "Stealth" and then add the external IP addresses as External Secondaries. |
| | |
| | |
| | Remember, if you have a third party DNS transferring from your NIOS external DNS servers, if the Grid Primary goes offline, the Grid Secondary will still get updated (via Grid Transfer). Enable Grid secondaries to notify external secondaries. |
| | |
| | Data Management > DNS > Grid DNS Properties > General > Advanced > |
| | * [[https://docs.infoblox.com/space/nios90/281182286/Notifying+External+Secondary+Servers|Enable Grid secondaries to notify external secondaries]]: This option is enabled by default. |
| | * Notify Delay: Specify the number of seconds that the Grid secondary servers delays sending notification messages to the external secondaries. The default is five seconds. |
| | |
| | "Enable grid secondaries to notify external secondaries: Select this check box to allow secondary name servers in a Grid to send notify messages to secondary name servers outside the Grid. Enabling this option increases the number of notify messages; however, it ensures that an external secondary name server receives notify messages when its master is a secondary name server in a Grid." |
| ===== DNS Views ===== | ===== DNS Views ===== |
| Multiple views on a member, fine. Looping/Forwarding between views is not fine. Possible and, in some cases, necessary, but not fine. It also means that the NIOS member probably cannot use itself as a resolver because it will often match the "wrong" view. | Multiple views on a member, fine. Looping/Forwarding between views is not fine. Possible and, in some cases, necessary, but not fine. It also means that the NIOS member probably cannot use itself as a resolver because it will often match the "wrong" view. |
| |
| If you need to increase, do so 1k at a time. | If you need to increase, do so 1k at a time. |
| | |
| | [[https://docs.infoblox.com/space/nios90/280665882/Enabling+Recursive+Queries|Documentation page]] |
| | Recursion client quota as printed in syslog |
| | <code> |
| | Recursion client quota: used/max/soft-limit/s-over/hard-limit/h-over/low-pri = 19005/23288/29900/0/30000/0/19005 |
| | |
| | |
| | /used /max /soft-limit /s-over /hard-limit /h-over /low-pri |
| | /21415 /24100 /29900 /0 /30000 /0 /21415</code> |
| | |
| | |
| | |
| | |
| |
| [[https://community.infoblox.com/t5/trending-kb-articles/support-central-kb-118-what-does-quot-no-more-recursive-clients/ba-p/6321|KB Article]] - If you want to increase the number of outstanding recursive queries on the recursive name server, confirm that you have adequate memory available for that number of outstanding recursive queries and for other services that are configured on the same server. Every recursive query can take about 20 kilobytes. | [[https://community.infoblox.com/t5/trending-kb-articles/support-central-kb-118-what-does-quot-no-more-recursive-clients/ba-p/6321|KB Article]] - If you want to increase the number of outstanding recursive queries on the recursive name server, confirm that you have adequate memory available for that number of outstanding recursive queries and for other services that are configured on the same server. Every recursive query can take about 20 kilobytes. |
