31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
|
Answer the following questions to describe your code submission. Please keep
|
||
|
|
all lines to a maximum of 80 characters wide.
|
||
|
|
|
||
|
|
1 - Explain how you convert the IP address 1.2.3.4 into the correct format for
|
||
|
|
a PTR request.
|
||
|
|
|
||
|
|
We reversed the IP address to 4.3.2.1 by tokenizing at the periods and
|
||
|
|
then putting them back in correct order. Then concatenated the string portion on to the end of that
|
||
|
|
in-addr.arpa. , to give 4.3.2.1.in-addr.arpa.
|
||
|
|
|
||
|
|
|
||
|
|
2 - Explain the fields of an SOA record. Which of these would be interpreted as
|
||
|
|
an email address and how so?
|
||
|
|
|
||
|
|
There are 7 different fields:
|
||
|
|
MNAME (The primary master name),
|
||
|
|
RNAME (The email address),
|
||
|
|
SERIAL (The version number of the zone data),
|
||
|
|
REFRESH (How often secondary servers check for updates),
|
||
|
|
RETRY (How long to wait before retrying after a failed refresh),
|
||
|
|
EXPIRE (How long secondary servers keep data if updates fail),
|
||
|
|
MINIMUM (Default TTL for negative responses).
|
||
|
|
|
||
|
|
The RNAME would be interpreted as the email address and you would replace
|
||
|
|
the first . with an @ to turn into the normal email address structure.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|