Auto Light Dark
Auto Light Dark

Installing a DNSSEC Trust Anchor in NIOS (2603)


Scenario

You have decided to enable DNSSEC validation for your NIOS Grid, so that all of your users can take advantage of DNSSEC to protect their recursive queries. Please perform the necessary steps to enable DNSSEC recursive validation in the NIOS Grid and verify that it is working.


Estimate Completion Time

  • 25 to 30 minutes

Credentials

Description

Username

Password

URL or IP

Grid Manager UI

admin

infoblox

https://10.100.0.100/

Requirements

  • Administrative access to the NIOS Grid

Learning Content

Lab Initiation

Access jump-desktop

Once the lab is deployed, you can access the virtual machines required for this activity. To begin, select VM List from the navigation bar at the top, locate jump-desktop, and click the green play icon to open its console. Log in to the Linux UI.

Img123-20260704-070502-20260704-083159.png

Username: training

Password: infoblox

Initiate lab

To initiate the lab, double-click the Launch Lab icon on the Desktop.

Launch Lab
Launch Lab

Choose the lab number from the list and click OK.

2026-07-04_12-37-31-20260704-070747.png

After clicking OK, you will see a pop-up message with a brief description of the lab task. If the description looks correct, click Yes to continue lab initiation.

image-20231122-140739.png

Lab initiation will take a couple of minutes to finish.

Once complete, you will see another pop-up message with the login credentials and the URL for the Grid Manager’s User Interface. Note that the credentials may differ from those from prior labs.

Screenshot 2024-05-06 at 3.16.57 PM.png


Tasks

  • Task 1: Validate recursion is working and DNSSEC validation is not enabled yet.

  • Task 2: Query a signed domain to check validation status.

  • Task 3: Obtain the current root trust anchor.

  • Task 4: Enable DNSSEC validation and install the trust anchor.

  • Task 5: Verify DNSSEC signed domains are now correctly validated.


Task 1: Verify recursion is enabled on the Grid

  • Verify recursion is enabled on DNS members.

Task 2: Query a known signed domain to check validation status

  • Query a known domain that has DNSSEC enabled (signed). Observe that no DNSSEC validation is being performed.

Task 3: Obtain the current root trust anchor

  • Use dig to query DNSKEYs for root (.) using a trusted DNS server.

  • Save the key information for later use.

Task 4: Enable DNSSEC validation and install the trust anchor

  • Enable DNSSEC validation on the Grid.

  • Install the root trust anchor.

Task 5: Verify DNSSEC signed domains are now validated

  • Use lookup tools to verify that DNSSEC validation is working correctly.


Solutions

Task 1 Solution: Verify recursion is enabled on the Grid

  1. Login to NIOS Grid UI (https://10.100.0.100) with the credentials admin/infoblox.

  2. Navigate to Data Managment → DNS → Members.

  3. Click the menu icon and choose to Edit the members ibns1.techblue.net and ibns2.techblue.net one at a time.

  4. In the Member DNS Properties dialog, select Queries tab on the left, verify the Allow recursion option is enabled. Do this for both members ibns1.techblue.net and ibns2.techblue.net.

    2026-09-10_15-04-01.png

Task 2 Solution: Query a known signed domain to check validation status

  1. Choose a domain that has been signed, or has authoritative DNSSEC enabled. We can verify the domain is signed by querying for its DNSKEY. This is just to verify that the domain (ietf.org in our example) has DNSSEC enabled. We do not care about the actual data returned, as long as we receive no errors and there are at least two DNSKEY records. You may use this dig command: dig @10.100.0.105 ietf.org. DNSKEY +multi

    2026-09-10_15-07-43.png


  2. Next, query the same domain and observe that the DNS header flags. Want to make sure there is no AD flag. This verifies that while recursion is working (RA flag is present), but no DNSSEC validation is performed on the resolver (no AD flag).

    2026-09-10_15-06-47.png

Task 3 Solution: Obtain the current root trust anchor

There are several methods to obtain root trust anchors. The easiest way is to query a public DNSSEC validating resolver. You may also query for the entire root zone file and extract the key (https://www.internic.net/domain/root.zone), or use a dedicated tool such as get-trust-anchor: https://github.com/iana-org/get-trust-anchor

Until January 2027, there will be two root Key Signing Key (KSK) in use. Make sure you select the one that appears in the screenshot that begins with the strings AwEAAa96jeu. The other KSK (that begins with AwEAAaz/tAm8y) will be retired after January 2027.

  1. Query Google Public DNS, which has DNSSEC validation enabled. Use this dig command to query for the root (.) key: dig @8.8.8.8 . DNSKEY

  2. The output will display multiple keys. We are looking for the Key Signing Key (KSK) with the key type 257.

    2026-09-10_14-31-42.png
  3. Open the application Geany from the applications menu.

    image-20230921-110129.png
  4. Copy the Key Signing Key (KSK) into Geany or a text editor to add later into NIOS. Make sure you copy the key that begins with AwEAAa96jeu.

Task 4 Solution: Enable DNSSEC Validation and Install the trust anchor

Until January 2027, there will be two root Key Signing Key (KSK) in use. It is okay to install both as trust anchors.

  1. Login back to NIOS Grid UI (https://10.100.0.100) with the credentials admin/infoblox.

  2. Navigate to Data Managment → DNS, then click Grid DNS Properties from the Toolbar.

    2026-09-10_15-26-52.png
  3. Toggle Advanced mode, and select the DNSSEC tab.

    2026-09-10_15-27-33.png
  4. Verify the chbox for Enable DNSSEC is checked. It should be checked by default.

  5. Scroll down and verify Enable DNSSEC Validation is checked. It should be checked by default. However, without a trust anchor, no validation is done.

    2026-09-10_15-28-30.png
  6. Click the + next to TRUST ANCHORS to add a new entry. You may have more than one trust anchor.

  7. The name of the zone is a single dot (.) for root.

  8. Copy the key string we saved earlier into the public key section.

    2026-09-10_14-54-55.png
  9. Take a note of the key algorithm used for the KSK we copied into Geany or text editor, and select the same key algorithm under the Algorithm section.

    2026-09-10_14-54-08.png
  10. Save and Close, then restart the service when prompted.

Task 5 Solution: Verify DNSSEC signed domains are now validated

  1. In a terminal window, use dig to query the same domain (www.ietf.org) tested earlier. If DNSSEC validation has been enabled correctly on the member, you should see the AD flag present in the response.

    2026-09-10_15-30-25.png