LDAP: couldn't connect to LDAP server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
opennic:tier1setup [2017-12-03T16:23:32Z]
adventure30 [named.conf]
opennic:tier1setup [2021-03-20T16:40:32Z] (current)
Shdwdrgn Updated root server IP
Line 5: Line 5:
 FIXME This legacy wiki article has been copied from http://web.archive.org/web/20161228061854/wiki.opennicproject.org/RunningT1. It is outdated and should not be blindly used for copy-pasting.  Use this information as a starting point to further researching current methods. FIXME This legacy wiki article has been copied from http://web.archive.org/web/20161228061854/wiki.opennicproject.org/RunningT1. It is outdated and should not be blindly used for copy-pasting.  Use this information as a starting point to further researching current methods.
  
 +But where, if not here, are those settings documented?
 ===== BIND9 setup ===== ===== BIND9 setup =====
 Setting up a OpenNIC Tier 1 server, requires creating slave zones for all the TLDs within the OpenNIC name-space. Setting up a OpenNIC Tier 1 server, requires creating slave zones for all the TLDs within the OpenNIC name-space.
Line 20: Line 21:
 Begin with the '.' root zone; add the following directive statement, to the BIND9 ("named") configuration file "named.conf". Begin with the '.' root zone; add the following directive statement, to the BIND9 ("named") configuration file "named.conf".
  
-== named.conf ==+== named.conf==
 <code> <code>
 zone "." { zone "." {
  type slave;  type slave;
  file "/etc/bind/zones/db.root";  file "/etc/bind/zones/db.root";
- masters { 75.127.96.89; };+ masters { 168.119.153.26; };
  allow-transfer { any; };  allow-transfer { any; };
  notify no;  notify no;
Line 31: Line 32:
 </code> </code>
  
-Below are the zones for each OpenNIC TLD.  Ad these to the //named// configuration file; "named.conf".+Below are the zones for each OpenNIC TLD.  Add these to the //named// configuration file; "named.conf".
  
 == opennic.glue == == opennic.glue ==
Line 38: Line 39:
  type slave;  type slave;
  file "/etc/bind/zones/slaves/glue.zone";  file "/etc/bind/zones/slaves/glue.zone";
- masters { 75.127.96.89; };+ masters { 168.119.153.26; };
  allow-transfer { any; };  allow-transfer { any; };
  notify no;  notify no;
Line 49: Line 50:
  type slave;  type slave;
  file "/etc/bind/zones/slaves/dns.glue.zone";  file "/etc/bind/zones/slaves/dns.glue.zone";
- masters { 75.127.96.89; };+ masters { 168.119.153.26; };
  allow-transfer { any; };  allow-transfer { any; };
  notify no;  notify no;
Line 305: Line 306:
 </code> </code>
  
-I hope that this guide has assisted getting your Tier 1 server ready for your new TLD. Remember to follow the insturctions on creating a new TLD if you have not already had your TLD approved for use within OpenNIC by vote of the membership. [[opennic:creating_new_tlds]]+I hope (likely in vain) that this guide has assisted (even though the the preface states that it is totally outdated) getting your Tier 1 server ready for your new TLD.  
 + 
 +Remember to follow the instructions on creating a new TLD in case you have not yet had your TLD approved for use within OpenNIC by vote of the membership. [[opennic:creating_new_tlds]]
  • /wiki/data/attic/opennic/tier1setup.1512318212.txt.gz
  • Last modified: 4 years ago
  • by adventure30