The DTC uses a MaxMind database for GeoIP information. The one that comes with NIOS is old.

You can sign up for a free account with MaxMind and download the free "lite" version of the database

When the DTC subscription expires, the expected behaviour is for the DTC service to stop working.

Data Management > DNS > Traffic Control > Manage Health Monitors > [Monitor Name] > Request / Response.

In the “HTTP Request Box”, don't forget that for proper monitoring you will need to include a second line with “HTTP/1.1” because, by default, DTC uses “HTTP/1.0”

Also, if there are multiple sites behind one IP, you may need to add the “HOST … ” line

e.g.

GET /app1.html
HTTP/1.1
HOST: www.example.corp

If you need to use HOST, you will probably need to form the config as follows:

GET http://www.dtc.example.corp/index.html
HTTP/1.1
HOST: www.dtc.example.corp

• You can choose up to 4 Extensible Attributes to use as source types for topology rules.
• GSLB results are returned only if the query resolves to an authoritative zone to which an LBDN is explicitly linked.
• DNS Traffic Control querying process is not supported for recursive queries.
• No authentication support in HTTP or HTTP/S monitor.
• No Automatic MaxMind updates. A single MaxMind DB per grid and only gets updated when anew version is manually uploaded. Please note- this does not need to be updated very often.
• The SIP monitor does not support SCTP transport.
• DNS Traffic Control license cannot be installed on the Infoblox 4030 appliance as it is intended as a caching only appliance.
• Infoblox does not support running DNS Traffic Control on the TE-810 and TE-820 appliances.
• DTC health monitoring does not monitor dual stack servers (supporting IPv4 and IPv6interfaces) if the Infoblox appliance health monitoring interface does not also have IPv4 andIPv6 IP stacks.
• The DNS Traffic Control does not support the Global application of an LBDN pattern against all queries. The appliance returns a result only if the query resolves to an authoritative zone to which an DNS Traffic Control LBDN is explicitly linked.

Best Practices To get the most from Infoblox DTC, Infoblox recommends the following best practices:

• A new DTC configuration should always be tested using the built-in LBDN test tool.
• For web application servers, HTTP and HTTP/S health monitors should be used to verify application level availability i.e. test for a specific string being returned rather than simply port80 availability.
• Always view the traffic management structures through the built-in hierarchical map view that can be used to quickly view the overall traffic management structure of a selected DNS Traffic Control Object.
• Use a naming convention for LBDN’s, and their associated Pools, Servers, and Topology rules.These naming conventions can be used for filtering within the GUI table views (they can be saved) and to identify a Server vs. Pool Topology rule

The following is when checking that GET works with specific match in body.

When the web server was broken by updating the page, the following message is generated.

• Facility : User
• Level: INFO
• Server: idns_healthd
• Message: [HTTP monitor 'web-test' checked 'web1' (web1.example.com:80), IPv4 status is OFFLINE (A match for the regular expression was 'not found' in the response. The configuration specifies 'found'.)]

When the page is restored, the following message is generated.

• Facility : User
• Level: INFO
• Server: idns_healthd
• Message: [HTTP monitor 'web-test' checked 'web1' (web1.example.com:80), IPv4 status is ONLINE]
• Message: [ICMP monitor 'icmp' checked 'web1' (web3.example.com:0), IPv4 status is ONLINE]