312-50V11 · Question #107
You have the SOA presented below in your Zone. Your secondary servers have not been able to contact your primary server to synchronize information. How long will the secondary servers attempt to…
The correct answer is C. One week. The SOA expire field (the fourth numeric value) defines how long secondary servers will attempt to refresh before treating the zone as dead.
Question
You have the SOA presented below in your Zone. Your secondary servers have not been able to contact your primary server to synchronize information. How long will the secondary servers attempt to contact the primary server before it considers that zone is dead and stops responding to queries? collegae.edu.SOA, cikkye.edu ipad.college.edu. (200302028 3600 3600 604800 3600)
Options
- AOne day
- BOne hour
- COne week
- DOne month
How the community answered
(33 responses)- A6% (2)
- B18% (6)
- C73% (24)
- D3% (1)
Why each option
The SOA expire field (the fourth numeric value) defines how long secondary servers will attempt to refresh before treating the zone as dead.
One day is 86400 seconds, which does not match the expire field value of 604800 seconds.
One hour is 3600 seconds, which matches the refresh and retry fields, not the expire field.
In the SOA record (200302028 3600 3600 604800 3600), the fields are serial, refresh, retry, expire, and minimum TTL respectively. The expire value is 604800 seconds, which equals exactly 7 days or one week - after this period without contact, secondary servers stop responding to queries for the zone.
One month would be approximately 2592000 seconds, far exceeding the expire value of 604800 seconds.
Concept tested: DNS SOA record expire field interpretation
Source: https://learn.microsoft.com/en-us/windows-server/networking/dns/zone-transfer
Topics
Community Discussion
No community discussion yet for this question.