Page MenuHomeMy privacy DNS

example.org.zone
ActivePublic

Authored by Spirillen on Feb 21 2021, 12:06 AM.
example.org. 86400 IN SOA ns1.example.org mail@example.org 2021021801 3600 600 1209600 3600
example.org. IN NS ns1.example.org.
example.org. IN NS ns2.example.org.
example.org. IN A 192.0.2.2
bad.example.org. IN A 192.0.2.3
god.example.org. IN A 192.0.2.4
example.org. 86400 IN MX 10 mail.example.org.

Event Timeline

Spirillen created this object with visibility "Public (No Login Required)".

The SOA record is the key informations for any given DNS zone and should be understood in the following way

  • SOA, this is where META information for the zone is
    • 86400 Time to live (TTL)
    • ns1.example.org The authoritative master DNS server for this domain
    • mail@example.org E-Mail address for who is in charge for example.org
    • 2021021801 a uniq key used to compare between AUTH and recurser server. If this number have crown (Should never be lowered), then there are changes to the zone records, and a refresh of zone data is required. (Fetch zone on new)
    • 3600 refresh, check for changes
    • 600 retry, if failed to connect
    • 1209600 expire, purge all stored data, if unable to update.
    • 3600 default_ttl

This zone is a direct refrence to RFC:2606: https://tools.ietf.org/html/rfc2606and RFC:5737: https://tools.ietf.org/html/rfc5737