AAC-007-05 Labguide - v2
AAC-007-05 Labguide - v2
Lab Guide
Infoblox Educational Services
Revision 007-5a
May 11, 2011
Copyright © 2011, Infoblox Inc. — All rights reserved.
The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written
permission of Infoblox, Inc.
The information in this document is subject to change without notice. Infoblox, Inc. shall not be liable for any damages
resulting from technical errors or omissions which may be present in this document, or from use of this document.
This document is an unpublished work protected by the United States copyright laws and is proprietary to Infoblox, Inc.
Disclosure, copying, reproduction, merger, translation, modification, enhancement, or use of this document by anyone
other than authorized employees, authorized users, or licensees of Infoblox, Inc. without the prior written consent of
Infoblox, Inc. is prohibited.
Infoblox, the Infoblox logo, DNSone, NIOS, Keystone, bloxSDB, bloxHA and bloxSYNC are trademarks or registered
trademarks of Infoblox Inc.
All other trademarked names used herein are the properties of their respective owners and are used for identification
purposes only.
Preface ..................................................................................................................1
DNSSEC ..............................................................................................................31
Views ..................................................................................................................53
Introduction
Welcome to the Advanced Administration Class Lab Guide. As you work your way through this guide
you will find both a return to familiar concepts from earlier labs and past classes as well as brand new
concepts. As you become reacquainted with those familiar topics we will attempt to stretch your
understanding and comprehension. As we familiarize you with new topics we will provide step-by-step
instructions to build your knowledge as well as your confidence.
© 2011 Infoblox Inc. All Rights reserved. 2
1 Lab 1
External Admin Authentication via Microsoft Active Directory
Introduction
Infoblox administrators can authenticate externally through an AD or RADIUS server.
Module Objectives
After successfully completing this module, you will be able to:
Configure an Infoblox admin account to authenticate via a Microsoft Active Directory server
• Configure an admin group on the Infoblox. This will determine the permissions for the user
• Specify the authentication servers that the Infoblox appliance will use, and in what order
• Create a policy that assigns the remote accounts to an Infoblox admin group so they can inherit
the right set the permissions.
Lab Setup
eLab has an Active Directory server already set up with an admin group called infoblox-students and
several user accounts called student1, student2, student3 etc. You will test your work at the end of the
lab exercise using these accounts.
5. Click Save & Close to save your work and close the panel.
7. Click the “+” (plus) button to open the Manage Global Permissions dialog box.
You are going to give this group read-only permissions for all DNS zones.
8. Change the drop-down menu under Permission Type to DNS Permissions and check the box
marked Read-Only next to All DNS Zones.
7. Click Test.
8. Click Add.
Note: You will get a message warning you about using unencrypted communication with the AD
server. Go ahead and click Yes to this.
The Policy editor also lets you define the Admin Group for remote administrators so that the right
privileges can be assigned to the admin account.
In this exercise, you create a policy that says “If a user authenticates via an AD server and the AD server
returns a group name infoblox-students, then assign them to the Infoblox group infoblox-students.”
1. Working within the Administrators and Authentication Policy panels of the Administration
panel look at the section that says “Authenticate users against these services in this order”.
The editor lets you add an Authentication Service you previously created.
3. In the Add Authentication Service section, click the Active Directory button.
4. Change the drop down box to niosrox-ad (the Active Directory Authentication service you
created earlier).
5. Click Add.
6. Click in the check box for the authentication service you added and hit the up arrow on the
left hand side of the screen until your policy is at the top of the list
9. Select infoblox-students.
These accounts should have read-only permissions for DNS Zones. Try creating some DNS Zones with
your local Admin account and then changing them with the student account. What was the result?
Record your results below.
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
________________________________________________________________
Introduction
An option space is a term that refers to a list of DHCP options. We typically deal with just one option
space - the Standard DHCP Option Space, made up of 254 options. The Standard Option Space is not
the only option space; many vendors have defined custom option spaces designed to meet the
specialized needs of devices like Wireless Access points and VOIP phones.
In this lab, we create a custom option space for a Cisco Wireless Access Point and configure the
appliance to serve options from this option space.
Infoblox provides a simpler method of creating custom DHCP option spaces using its “Advanced DHCP
Options” feature. The Advanced DHCP Options feature essentially translates Option 43 for you into
simple, non-hex language.
Module Objectives
In this lab, you create a custom option space for a Cisco wireless access point. Your next task will be to
add options to the option space. Afterwards, you will configure a “match filter” (a rule) that will look
for client DHCP Discovers that include DHCP Option 60 (the vendor-class-identifier). When a client
sends a Discover containing DHCP Option 60 that identifies the client device as a Cisco device, your
appliance will serve the custom options you defined in your option space.
When you finish your work, you will compare your settings in the dhcpd.conf file and see how they
compare to a correctly configured the dhcpd.conf file.
9. Change the drop down menu from the Code section to 241.
10. Change the drop down menu from the Type section to array of ip-address.
11. Click Save & Close to save your new option/option space.
In this exercise, you create an option filter called Cisco Aironet 1130 Series.
1. Within the Data Management panel, in the DHCP and Filters/Option Spaces panels, expand
the section marked Filters.
3. In the Name box, enter the name Cisco Aironet 1130 Series.
7. Click the Save & Close button. (Next would bring you to Extensible Attributes.)
3. Change the Match Option drop down menu to vendor-class-identifier (60) string.
4. In the Match Value box, enter the string to be matched. For this exercise, enter the following:
Cisco AP c1130
1. In the Networks panel, click on the network that contains the range you created earlier.
If you are following the example, then the network is 10.34.10.0 /24.
2. Select the range you created earlier and click the edit icon.
If you are following the example, the range is 10.34.10.1 to 10.34.10.10.
3. Click on DHCP and scroll down to the Custom DHCP Options section
4. Select Cisco-Aironet (the option space), Controller_IP (as the option), and enter the value
10.34.1.3,10.34.1.4
6. Click on the Restart button at the top left corner of the screen to restart DHCP and use your new
configuration.
Challenge 1: Configure DHCP Option Filters for Cisco AP 1240 & 1500
The following challenges are based on data provided below. If you look through the data, you will see
details about the Cisco 1130 wireless access point and about two other Cisco AP models: the 1240 and
the 1500.
Use this data and the procedure in the preceding exercise to configure custom options for the Cisco 1240
and 1500 wireless access points. Afterwards, create option filters using the IP address ranges shown
below.
Vendor Option 241 on all ranges should have a value of: 10.40.255.160,
10.40.255.161, 10.40.255.162, 10.40.255.163
Introduction
In this lab you will enable TSIG and GSS-TSIG on your DNS zones and DHCP ranges.
Module Objectives
After successfully completing this module, you will understand the process of enabling TSIG and GSS-
TSIG on your appliances. You will complete the following tasks:
• Successfully load a GSS-TSIG Keytab file and enable it at the Grid level
3. Click on the drop down arrow next to the “+” (plus) button in the Updates section.
6. Click Generate Key Data (or click on the down arrow of the Generate Key Data to choose the
key length) NOTE: If you were really setting up TSIG updates you would need to copy this
key to the DNS server you wanted to provide updates to your appliance.
7. Click Add.
• User: ftp
• cd AAC
• prompt
• bin
• mget *.*
• quit
2. Switch to the DHCP and Network Panel in the Data Management panel.
9. Click Ok.
11. Change the GSS-TSIG Key to the keytab you just loaded.
NOTE: You will not be able to test GSS-TSIG at this time
12. Click Save & Close.
Introduction
In this lab, we will use the DHCP server to send Dynamic DNS (DDNS) updates when clients get IP
addresses. We will try using both non-option 81, and option-81.
Module Objectives
After successfully completing this lab, you will be able to:
Successfully configure the Infoblox Appliance so that your virtual Windows XP machine gets and IP
address via DHCP and registers itself in the DNS server. A, PTR, and TXT records should be visible in
the UI using the zone information configured on the Infoblox appliance.
Successfully configure the Infoblox Appliance so that your virtual Windows XP machine gets an IP
address via DHCP and registers itself in the DNS server. A, and PTR records should be visible in the UI
using the zone information entered on the Windows machine (option-81 enabled).
NOTE: Before attempting to do this lab, it is VERY important that you disable GSS-TSIG that you
enabled in the previous lab. Follow the steps from the previous lab and uncheck the checkbox where
you enabled GSS-TSIG.
b. Create a reverse mapping zone 10.100.x.0 /24 where x is your student number.
c. Assign your appliance as the Primary Name Server for the zones you created above.
a. Configure your Infoblox device to send the domain name studentXX.lab to the client
device (where XX is your student number.)
3. In the Networks panel, configure a network with the following address: 10.100.x.0 /24 where x
is your student number. Your appliance will assign an address to your XP machine from this
network. While creating the network, also do the following:
b. Configure the router IP address (the routers IP ends in “.1” for all eLab networks)
5. Configure your Windows XP machine to use DHCP and make sure your device gets an address.
6. After getting an address, check to see that the client FQDN is correct and that the following
records have been added to DNS: A, TXT, and PTR record.
1. Configure your Windows XP client so that it will send the FQDN and will use the DNS suffix of
“aac.lab.”
b. Delete the PTR record that was created in exercise 1 in the reverse zone for 10.100.x.
3. In the DHCP panel, remove the domain name “studentXX.lab” and uncheck the box marked
Override Grid Domain Name.
6. Create a new range making sure not to use the IP address that was assigned to your Windows XP
client.
7. Open the Toolbar panel under the DHCP panel. Afterwards, click on Configure DDNS.
Specify “aac.lab” as the zone to update. Save your work and restart services.
d. Verify that your XP client received an IP address and was assigned the domain suffix
“aac.lab.” Then check that your machine was registered in to the correct forward and
reverse zones.
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
________________________________________________________________________
Introduction
DNS Security Extensions (DNSSEC) allows Zone administrators to digitally sign zone data and thereby
enhance its security and integrity.
Module Objectives
After successfully completing this module, you will be able to:
• Understand DNSSEC.
• See how the “chain of trust” works between a parent and child domain.
Exercise 1: Use DIG to query the BIND server for the zones n-sec and n-sec3. These are fictitious
top-level domains that have been secured with DNSSEC.
Exercise 2: Configure your appliance to function as a secondary for the n-sec3 zone.
1. Click Start....Run.
4. Retrieve the SOA record from the Infoblox DNSSEC DNS server by typing
“dig @198.107.144.70 n-sec soa”.
198.107.144.70 is the DNSSEC DNS server. N-sec is the name of the zone that you are
querying.
1. On your appliance, enable DNSSEC. Make sure that DNSSEC validation is also enabled.
a. Go to the Data Management panel, and then select the DNS panel.
c. Select DNSSEC, and then Check the Enable DNSSEC box, and the Enable DNSSEC
validation box.
2. On your appliance, create a zone called n-sec3 and list the Infoblox DNSSEC DNS server as
an external primary and your appliance as the secondary. Here are the details:
Zone Name: n-sec3
3. Type “dig @<Your-Infoblox-Appliance-IP> n-sec3 soa” to verify that you can get a
response.
4. From the GUI, look at the types of records, and the number of records that are in this zone.
5. What evidence is there (besides the zone’s name) to tell if this is an NSEC or NSEC3 signed
zone?
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
b. Under the Zones panel, click the arrow next to the “+” plus sign.
5. Type “dig @<Your-Infoblox-Appliance-IP> n-sec soa” and verify you are getting a
response.
10. Once logged in, you are going to get a file called DNSSEC-lab-keys.txt that holds the
“trusted keys” for the n-sec zone. Run the following commands. (Note that they are case-
sensitive.)
• cd DNSSEC
• get DNSSEC-lab-keys.txt
The GET command places the file here: C:\Documents and Settings\training\Desktop.
12. Return back to the NIOS GUI, and open the Toolbar (if no already open).
14. Go to DNSSEC and click the “+” (plus) button next to Trust Anchors.
16. Click Save & Close. (Do you need to restart services????)
18. Open a DOS prompt on your Windows system and type “dig @<Your-Infoblox-Appliance-
IP> n-sec soa” and verify you are getting a response.
19. Download the traffic capture. Make sure you do not save it over the traffic capture you took
earlier.
b. Right-click on the tcpdumpLog.tar file and select “7-Zip Æ Extract Here” again to
create a traffic.cap file.
c. Rename this file so you do not overwrite it. Then extract the second traffic capture.
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
3. Look at the results. Notice anything different? What can be said about the A record
dhcp.test.n-sec?
2. Select the signed.studentXX.tld zone (check the box to the left of it)
3. Go to the Toolbar and select the drop down arrow next to DNSSEC.
5. That will launch the Sign Zone dialog box. Click on Sign Zone again.
a. Notice the NSEC record for that new record is automatically added
b. The “previous” record will automatically get a new NSEC record, too, pointing to the
new record as the “NEXT” record in the zone
Unzip the traffic capture you take using 7-zip, as you did in the previous exercises, and trace the
conversation that takes place to validate the response from the dig command.
Introduction
Infoblox uses anycast to provide reliable DNS service. Anycast enables a group of appliances to share a
common address and to appear to clients as a single entity. When clients send queries to the anycast
address, the queries do not go to the group but are instead are routed to the “nearest” server within the
anycast group. Anycast thus ensures the fastest possible resolution to queries and provides a mechanism
for recovering from server failures. When one server fails, DNS queries are automatically rerouted to
one of the surviving servers.
• Configure an anycast IP address on the loopback interface. This address will be shared by all of
the servers in your anycast group
• Configure the appliance to use OSPF to advertise routing information to the upstream router
In the exercise, you will configure the anycast address on the loopback interfaces of your servers. Then
you will configure your appliance to use OSPF so it can advertise the anycast address to the upstream
router. Afterwards, you “turn on” anycast by configuring DNS services to listen for queries sent to the
anycast address. When you and your partner have finished configuring your appliances, you will test
your setup by using DIG to query the anycast IP address and seeing which of the two servers responds.
5. Click on the “+” (plus) button under the Anycast Interfaces section.
a. Area ID = 0.0.0.0
d. Key ID = 1
e. Key = anycast
g. Hello Interval = 10
h. Dead Interval = 40
i. Retransmit Interval = 5
j. Transmit Delay = 1
1. Go to the Data Management panel, and the Members panel underneath the DNS panel.
3. Click the Advanced Tab at the top of the Members DNS Properties panel.
5. Click on the “+” plus button under the Listen on These Additional IP Addresses section.
2. Disable DNS
a. Go back and disable your appliance from using DNS.
Hint: Stop DNS from listening on the Anycast IP, or turn off DNS.
b. Now go back and look at the routers routing table.
c. What changed? Do you still see your route?
Introduction
In this lab, you will create views.
Module Objectives
After successfully completing this module, you will be able to:
1. Open the Data Management panel, then the DNS panel and then the Members panel.
2. In the menu, click the down arrow next to the Add command and then select Add DNS View
from the sub-menu.
A wizard opens
5. Click the downward arrow in the Add button (+) and select IPv4 Address from the menu.
7. Click Save & Close (we don’t need to add any extensible attributes.)
8. Restart services.
Exercise 2 – Add a Zone and Some Records to the New DNS View
Add a zone and an A record to your new DNS View.
2. Click the Add button (+) and select Authoritative Zone from the menu.
3. When the wizard opens, enter a zone name (make one up) and assign your appliance as the
Primary nameserver. Afterwards, save and close the wizard.
5. Restart services.
4. Click the text marked Toggle Advanced Mode in the top right corner.
6. When the DNS Views page opens, check the radio button labeled Order DNS Views
automatically.
8. Restart services.
1. Open the Administration panel and then the Network Views panel.
2. Click the “+” (plus) button to launch the Add Network View Wizard.
3. Enter StudentX_CompanyB for the new Network View’s name, where X = your assigned
student number.
5. Rename the default Network View to StudentX_CompanyA, where X = your assigned student
number.
6. Restart services.
4. Add a new DNS view called CompanyB_External to the StudentX_CompanyB Network View.
6. Restart services.
1. Under the StudentX_CompanyA network view in the Zones panel, open the DNS View you
created earlier.
2. In your DNS View, create an authoritative forward mapping zone. This will be the destination
for your copied records.
3. Restart services.
4. Add a check to the box next to the source zone that has some manually created records in it.
Note that you can not copy auto-generated records.
6. In the dialog box that opens, select the destination zone that you just created.
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
Introduction
In this lab, you will build a Grid, configure a DHCP Failover association, and use the DHCP Failover
Association when creating DHCP ranges.
Module Objectives
After successfully completing this module, you will be able to:
• Create DHCP Failover Associations on both the primary and secondary DHCP servers. This
only needs to be done once if the primary and secondary servers are both in a grid.
5. In the Name field, fill in FA-xx-yy where “xx” is your student # and “yy” is your peers student
#. Remember that you are now in a grid and each DHCP Failover association name must be
unique!
6. Using the “Select member…” button, select your device as the Primary.
This assigns the local device as the primary DHCP server.
7. Using the “Select member…” button, select the Grid Master as the Secondary.
It is very important that you choose the Grid Master as the secondary.
10. Edit the Failover Association and change the MCLT value to 5 minutes.
NOTE: This is NOT a recommended value and is being used for lab purposes only!
b. If you don’t see an Advanced tab at the top, click on the Toggle Expert Mode link
d. Change the value for Maximum Client Lead Time (s) from the default value of 3600 (1
hour) to 300 (5 minutes)
c. Make sure the Network is assigned to both members of your DHCP Failover association
d. Make sure the DHCP Range is assigned to the DHCP Failover association
1. Go back to Failover Associations section of the DHCP and Members Panels (where you
created your association earlier)
3. Next go to the Syslog and review the messages related to your association.
6. Does the status of the association change? What Syslog messages do you see on the Grid
Master, and on your member (after it comes back up) in regards to the DHCP failover
association?
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
1. The instructor, or one of the students should disable DHCP on the Grid Master.
The end result is that all Failover Associations should show Communication-Interrupted for the
Primary member, assuming that everyone used the Grid Master as the Secondary.
2. Once you have confirmed that the secondary peer is not reachable (DHCP has been disabled, in
this lab to emulate an unreachable/unavailable server), place the remaining peer in Partner-
Down. We are assuming the Grid Master really is not available, so using the GUI should NOT
be an option. Using PuTTy, connect to the Console and run the command: set partnerdown
3. When asked to enter the failover association name, enter the name you gave the Failover
Association.
5. After the entire class has validated the Partner-Down state, the instructor should re-enable DHCP
on the Grid Master.
Results
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
Student IP Assignments
Introduction
This appendix presents the IP addresses you will be using in eLab.
10. LAN1 – This is your original address. Use this when your appliance is not in an HA pair.
11. HA – You will need this and the VIP for the HA exercise.
12. VIP – This is the address that you and your partner should share in the HA exercise.
Remote Virtual
Student
Desktop LAN HA VIP Router
Number
Profile ID
1 training-xp01 192.168.1.10 192.168.1.11
192.168.1.14 14
2 training-xp02 192.168.1.12 192.168.1.13
3 training-xp03 192,168.1.15 192.168.1.16
192.168.1.19 19
4 training-xp04 192.168.1.17 192.168.1.18
5 training-xp05 192.168.1.20 192.168.1.21
192.168.1.24 24
6 training-xp06 192.168.1.22 192.168.1.23
7 training-xp07 192.168.1.25 192.168.1.26
192.168.1.29 29
8 training-xp08 192.168.1.27 192.168.1.28
9 training-xp09 192.168.1.30 192.168.1.31
192.168.1.34 34
10 training-xp10 192.168.1.32 192.168.1.33
11 training-xp11 192.168.1.35 192.168.1.36
192.168.1.39 39
12 training-xp12 192.168.1.37 192.168.1.38
13 training-xp13 192.168.1.40 192.168.1.41
192.168.1.44 44
14 training-xp14 192.168.1.42 192.168.1.43
15 training-xp15 192.168.1.45 192.168.1.46
192.168.1.49 49
16 training-xp16 192.168.1.47 192.168.1.48
17 training-xp17 192.168.1.50 192.168.1.51
192.168.1.54 54
18 training-xp18 192.168.1.52 192.168.1.53
19 training-xp19 192.168.1.55 192.168.1.56
192.168.1.59 59
20 training-xp20 192.168.1.57 192.168.1.58
21 training-xp21 192.168.1.60 192.168.1.61
192.168.1.64 64
22 training-xp22 192.168.1.62 192.168.1.63
23 training-xp23 192.168.1.65 192.168.1.66
192.168.1.69 69
24 training-xp24 192.168.1.67 192.168.1.68
25 training-xp25 192.168.1.70 192.168.1.71
192.168.1.74 74
26 training-xp26 192.168.1.72 192.168.1.73
27 training-xp27 192.168.1.75 192.168.1.76
192.168.1.79 79
28 training-xp28 192.168.1.77 192.168.1.78
29 training-xp29 192.168.1.80 192.168.1.81
192.168.1.84 84
30 training-xp30 192.168.1.82 192.168.1.83
31 training-xp31 192.168.1.85 192.168.1.86
192.168.1.89 89
32 training-xp32 192.168.1.87 192.168.1.88
33 training-xp33 192.168.1.90 192.168.1.91
192.168.1.94 94
34 training-xp34 192.168.1.92 192.168.1.93
35 training-xp35 192.168.1.95 192.168.1.96
192.168.1.99 99
36 training-xp36 192.168.1.97 192.168.1.98
37 training-xp37 192.168.1.100 192.168.1.101
192.168.1.104 104
38 training-xp38 192.168.1.102 192.168.1.103