Learning Outcomes
- describe the role of the following in the DNS: registry, registrar, and registrant
- explain the role of root name servers, top level domain servers, and authoritative name server
- explain the process of recursive DNS resolution
- register a second level domain
- configure resource records (RR) of the following types for an application: SOA, A, CNAME, MX, NS, TXT, AAAA
- retrieve DNS information using
dig
Resources
- Pro DNS and BIND 10 I recommend that you read chapters 1 and 2 and the sections on the DNS protocol and DNS queries from chapter 3.
- How a DNS Server works. (video)
- slides
Lab
None.
Assignment
- In a text file answer the following questions:
- What is the phone number of the DNS technical contact for
amazon.com? - What are the name server records for
sfu.ca? - What are the mail exchanger records for
uvic.ca? - What kind of record is
stream.langara.ca?
- What is the phone number of the DNS technical contact for
- If you have not already done so, resize your
lab1VM down to a “f1-micro” instance type and create an “A” DNS record formyapp.4949NN.xyzwith the external IP address of yourlab1VM so that the application works by its domain name. - In your local development environment or Google Cloud Shell, create a new ExpressJS applicaiton,
mysecondapp. - Start the application listening on port 8081.
- Use web preview to test the application.
- Implement the
/webhookroute for this application exactly the same way as formyapp. You can copy the code and thedeploy.shscript. - Create a new GitLab project
mysecondappand follow the instructions to do the initial stage, commit, and push. - Create new firewall that allows traffic in on port 8081.
- Deploy
mysecondappto yourlab1VM by hand on port 8081. - Create a new “CNAME” record for
mysecondapp.4949NN.xyzthat points tomyapp.4949NN.xyz.