A customer requested to have certain DNS queries point to a different DNS server rather than the primary DNS server.

In this example, we will configure *.widgets.com to go to an alternate DNS server 4.2.2.2 and everything else will go to 8.8.8.8

Client attempts to go to neverssl.com, the DNS query looks like this: client --> rXg --> 8.8.8.8
The same client attempts to go to store.widgets.com, the DNS query will look like this: client --> rXg --> 4.2.2.2

This document was written and tested using the following components from the RG Nets.

RG Nets | rXg | 13.2 - 15.271

In the image above, there are several things to take note of.  The configuration in this section will send DNS queries for widgets.com or a sub-domain of widgets.com to the DNS server 4.2.2.2 and a backup of 4.2.2.3. The Master hostname is just the FQDN of the system.  The type should be set to forward.

This image shows a ping being sent to store.widgets.com which requires DNS resolution.

This image shows my lab rXg reaching out to 4.2.2.2 to resolve store.widgets.com.  The primary DNS server for this lab system is 8.8.8.8