Revision history for DNSSRVOperation
Revision [3745]
Last edited on 2016-05-30 22:49:37 by AlexHanselka [Replaces old-style internal links with new pipe-split links.]Additions:
- Be a member of the [[http://lists.darkdna.net/mailman/listinfo/dns-operations | dns-operations]] and [[http://lists.darkdna.net/mailman/listinfo/dns-reports | dns-reports]] OpenNIC mailing list.
- Provide, at least 1 business day advance warning to other operations personnel when conducting routine maintenance that may impact the operation of the server by posting notice of such to the mailing list (Email templates can be found [[emailtemplates | here]], discuss@lists.opennicproject.org. In addition, all scheduled maintenance outages of the DNS should be coordinated to minimize the effects of those outages on regular OpenNIC DNS operations.
- Provide, at least 1 business day advance warning to other operations personnel when conducting routine maintenance that may impact the operation of the server by posting notice of such to the mailing list (Email templates can be found [[emailtemplates | here]], discuss@lists.opennicproject.org. In addition, all scheduled maintenance outages of the DNS should be coordinated to minimize the effects of those outages on regular OpenNIC DNS operations.
Deletions:
- Provide, at least 1 business day advance warning to other operations personnel when conducting routine maintenance that may impact the operation of the server by posting notice of such to the mailing list (Email templates can be found [[emailtemplates here]], discuss@lists.opennicproject.org. In addition, all scheduled maintenance outages of the DNS should be coordinated to minimize the effects of those outages on regular OpenNIC DNS operations.
Revision [2944]
Edited on 2012-07-27 09:15:23 by AlexHanselka [Replaces old-style internal links with new pipe-split links.]Additions:
- Be a member of the [[http://lists.darkdna.net/mailman/listinfo/dns-operations dns-operations]] and [[http://lists.darkdna.net/mailman/listinfo/dns-reports dns-reports]] OpenNIC mailing list.
- Have introduced yourself to the OpenNIC membership via the mailing list.
- Have a static IP address.
- Maintain a stable up time.
- Have introduced yourself to the OpenNIC membership via the mailing list.
- Have a static IP address.
- Maintain a stable up time.
Deletions:
- Have introduced yourself to the OpenNIC membership via the mailing list.
- Have a static IP address.
- Maintain a stable up time.
- Limit non-emergency outages to the OpenNIC "maintenance window"(Last week in every month).
Additions:
- Be a member of the [[http://lists.darkdna.net/mailman/listinfo/dns-operations dns-operations]] and [[http://lists.darkdna.net/mailman/listinfo/dns-reports dns-reports]] OpenNIC mailing list.
- Have introduced yourself to the OpenNIC membership via the mailing list.
- Have a static IP address.
- Maintain a stable up time.
- Have introduced yourself to the OpenNIC membership via the mailing list.
- Have a static IP address.
- Maintain a stable up time.
Deletions:
- Have introduced yourself to the OpenNIC membership via the mailing list
- Have a static IP address
- Maintain a stable up time
Additions:
- Be a member of the [[http://lists.darkdna.net/mailman/listinfo/dns-operations dns-operations]] OpenNIC mailing list
- Have introduced yourself to the OpenNIC membership via the mailing list
- Have introduced yourself to the OpenNIC membership via the mailing list
Deletions:
Revision [1909]
Edited on 2009-05-25 21:31:11 by JulianDemarchi [removed criteria as it should not have been in here yet.]Deletions:
Additions:
OpenNIC's DNS services are offered by OpenNIC's users. All DNS servers operating under OpenNIC by its users must adhere to the following policy. OpenNIC would encourages it's members who run an OpenNIC DNS server to partake in an active role in the operation and responsibility of running the server.
This includes:
- Keeping abreast of DNS security issues and applying security updates as necessary.
- Becoming familiar with DNS structure and operation by referencing the official Internet Standards documents on DNS. Internet Standards are defined within documents entitled "Request for Comments" (RFC). Refer to the list of RFC references pertaining to the operation of DNS. - http://wiki.opennic.glue/HostmasteringWG
- Tier1 servers are required to be authoritative for each TLD OpenNIC operates
- Daily sending of query log files to OpenNIC central DNS log server
- Performing timely maintenance of DNS information (Inverse File Updates).
All potential DNS server operators must meet the following criteria:
- Have a static IP address
- Maintain a stable up time
- Be willing to submit your DNS query logs nightly to OpenNIC
All OpenNIC Domain Name Server Operators will:
- Provide and maintain adequate hardware in order to support the DNS server
- Maintain physical security of the network and DNS server hardware.
- Maintain the highest level of security on the DNS server, including monitoring the system and applying security patches to the Operating System and server software on a timely basis as needed, unless directed otherwise by OpenNIC.
- Maintain up to-date zone information, including the servers hint file (if in use)
- Limit non-emergency outages to the OpenNIC "maintenance window"(Last week in every month).
- Provide, at least 1 business day advance warning to other operations personnel when conducting routine maintenance that may impact the operation of the server by posting notice of such to the mailing list (Email templates can be found [[emailtemplates here]], discuss@lists.opennicproject.org. In addition, all scheduled maintenance outages of the DNS should be coordinated to minimize the effects of those outages on regular OpenNIC DNS operations.
This includes:
- Keeping abreast of DNS security issues and applying security updates as necessary.
- Becoming familiar with DNS structure and operation by referencing the official Internet Standards documents on DNS. Internet Standards are defined within documents entitled "Request for Comments" (RFC). Refer to the list of RFC references pertaining to the operation of DNS. - http://wiki.opennic.glue/HostmasteringWG
- Tier1 servers are required to be authoritative for each TLD OpenNIC operates
- Daily sending of query log files to OpenNIC central DNS log server
- Performing timely maintenance of DNS information (Inverse File Updates).
All potential DNS server operators must meet the following criteria:
- Have a static IP address
- Maintain a stable up time
- Be willing to submit your DNS query logs nightly to OpenNIC
All OpenNIC Domain Name Server Operators will:
- Provide and maintain adequate hardware in order to support the DNS server
- Maintain physical security of the network and DNS server hardware.
- Maintain the highest level of security on the DNS server, including monitoring the system and applying security patches to the Operating System and server software on a timely basis as needed, unless directed otherwise by OpenNIC.
- Maintain up to-date zone information, including the servers hint file (if in use)
- Limit non-emergency outages to the OpenNIC "maintenance window"(Last week in every month).
- Provide, at least 1 business day advance warning to other operations personnel when conducting routine maintenance that may impact the operation of the server by posting notice of such to the mailing list (Email templates can be found [[emailtemplates here]], discuss@lists.opennicproject.org. In addition, all scheduled maintenance outages of the DNS should be coordinated to minimize the effects of those outages on regular OpenNIC DNS operations.
Deletions:
~&More of an intro needed.
====What OpenNIC Requires====
OpenNIC does require feedback from DNS operators. We require DNS query log files to be sent to a central log server nightly.
~&Can't really word what I want to say. Here is what I wanna say, if you can put it into formal text please help;
~& I would like all DNS operators to SCP their DNS query log file to a central server nightly, so I may analyze them to determine the amount of quires on a whole OpenNIC is receiving along with other statistical information. I will also publicly display these reports, as the public have every right to view them if they wish.
Additions:
~&More of an intro needed.
====What OpenNIC Requires====
OpenNIC does require feedback from DNS operators. We require DNS query log files to be sent to a central log server nightly.
~&Can't really word what I want to say. Here is what I wanna say, if you can put it into formal text please help;
~& I would like all DNS operators to SCP their DNS query log file to a central server nightly, so I may analyze them to determine the amount of quires on a whole OpenNIC is receiving along with other statistical information. I will also publicly display these reports, as the public have every right to view them if they wish.
====What OpenNIC Requires====
OpenNIC does require feedback from DNS operators. We require DNS query log files to be sent to a central log server nightly.
~&Can't really word what I want to say. Here is what I wanna say, if you can put it into formal text please help;
~& I would like all DNS operators to SCP their DNS query log file to a central server nightly, so I may analyze them to determine the amount of quires on a whole OpenNIC is receiving along with other statistical information. I will also publicly display these reports, as the public have every right to view them if they wish.
Deletions:
Additions:
This policy covers the operation of an OpenNIC DNS server. It covers what OpenNIC expects from DNS operators, and the regulations for running an OpenNIC DNS server.
More of an intro needed.
More of an intro needed.
