Backgroound Image

ThousandEyes Walkthrough Part 4.3.2 Scenario 2 – Enterprise DNS test configuration

This post will go over the second scenario for the ThousandEyes lab. To see all the posts in this series expand the box below.

ThousandEyes Walkthrough Table of Contents

There are some behind-the-scenes posts that go into more detail on how and why I took the approach that I did. Those can be found here:

Scenario 2

Scenario: It’s known that critical applications are dependent on other network services, but there is a concern that the underlying services aren’t able to support the applications.
Technical requirements: DNS has been identified as a critical service that other applications are dependent on. The CML.LAB domain must be monitored for availability and performance.
All of the scenario information can be found in this post:
This scenario provides a few options for tests. An agent-to-server test could be used, but those tests don’t give DNS-specific info. Also, DNS could use UDP, and agent-to-server tests do not support UDP.  A DNS Server test would check for DNS server connectivity, and identify if a change was made to a DNS record.  That meets the objective of the scenario, so that’s the test we’ll set up.

Create an Enterprise DNS Server test

  1. Log in to ThousandEyes (I presume this skill has been mastered by now)
  2. On the left side, expand the menu, then click on Cloud and Enterprise Agents to expand that list, and then click Test Settings
  3. Click Add New Test.
  4. This will be a DNS Server test. Click DNS for the Layer, and then DNS Server for the Test Type
    1. Enter a name for the test
  5. Under Basic Configuration, in the Domain field enter cml.lab
    1. Leave the record options as default, IN and A
    2. NOTE: This is an internal domain that can’t be resolved by the ThousandEyes cloud. It will show a warning that it is unable to resolve the target. That warning can be ignored.
  6. As before, set the interval to 30 minutes to reduce the test load
  7. In the Agents field, select all the enterprise agents deployed
  8. Enter the lab DNS server IP in the DNS Servers field:
  9. Uncheck the Enable box for alerts
  10. When complete it should look like this:
  11. Click Create New Test
This will create the new test, and it will start running right away. Just like the agent-to-agent tests, this test can be disabled to save test units if it’s not being used.

Leave a Reply

Your email address will not be published. Required fields are marked *