Exercise 4: Edge DNS

Create an primary zone

First off, let's create a primary zone. Don't worry about the fact that this is not a real zone, but you will need to pick a zone name that doesn't already exist. I'd recommend <your username>.test or something similar. As with most APIs we cover, you will also need a contract ID and group ID, which can be retrieved with Get-Contract and Get-Group respectively.

The command you need to create a zone is New-EDNSZone.

Do so in an account that has Edge DNS on contract, but only use an internal account. APIs make life much easier, but also make it much easier to cause all kinds of disastrous carnage...

Create the necessary NS and SOA records

As mentioned in the guide, when you create a primary zone it comes with no records whatsoever. But, you will need NS and SOA records for a valid zone.

Hint: the commands for this are in the guide, so give it a read if you haven't already.

Add a few records

Add records of the following types and targets. You can use any TTLs you choose. Records named @ are apex records so their -Name value will be simply the zone name.

The A record has multiple targets, which is supported by the -RData parameter, so long as you have multiple strings separated by commas, rather than one string which contains commas. For example -RData '1.2.3.4', '2.3.4.5' is valid, but -RData '1.2.3.4, 2.3.4.5' is not.

Retrieve your DNS records

You should now be able to list all records in your zone, and see both the NS and SOA records, and the ones you just created. Do so now.

Change the TTL on your CNAME records

Set the TTL on your CNAME records to 3600 seconds.

Be careful when using Set-EDNSRecordSet. If you give it one record it will replace that record. If you give it more than one record, it will (with your approval) replace ALL records in your zone with just those 2, which we don't want. Structure your commands to accomodate.

Delete your zone.

This is reasonably uncommon in the real world, but we want to tidy up after ourselves, so remove your zone.