Revision history for Tier2ConfigBindSlave


Revision [3906]

Last edited on 2017-03-03 14:36:41 by JonahAragon [Added the "libre" zone]
Additions:
zone "libre" in {
file "libre.zone";

Revision [3897]

Edited on 2017-01-26 06:50:54 by Luggs [updated server test url]
Additions:
If you are creating a public tier-2, and have your firewall or port-forwarding configuration completed, you can test the public access of your service by visiting http://opennicproject.org/t2log/ and entering your IP address. If there are any failures you cannot resolve, please visit the mailing list or IRC to get help.
Deletions:
If you are creating a public tier-2, and have your firewall or port-forwarding configuration completed, you can test the public access of your service by visiting http://opennicproject.org/t2log/test.php and entering your IP address. If there are any failures you cannot resolve, please visit the mailing list or IRC to get help.

Revision [3786]

Edited on 2016-05-30 22:49:37 by JeffTaylor [Replaces old-style internal links with new pipe-split links.]
Additions:
For those wishing to set up a more robust local nameserver, or if you plan on running a public tier-1 or tier-2 server for OpenNIC, configuring BIND with slave zones is the preferred method. Please read the [[DNSSRVOperation | policies]] before running a public T2 server. You should also join the appropriate [[MailingLists]] so you'll be notified of changing situations which may affect your operation.
Deletions:
For those wishing to set up a more robust local nameserver, or if you plan on running a public tier-1 or tier-2 server for OpenNIC, configuring BIND with slave zones is the preferred method. Please read the [[DNSSRVOperation policies]] before running a public T2 server. You should also join the appropriate [[MailingLists]] so you'll be notified of changing situations which may affect your operation.

Revision [3655]

Edited on 2015-11-16 13:04:49 by JeffTaylor [Updated TLD zone list]
Additions:
zone "bit" in {
file "bit.zone";
zone "chan" in {
file "chan.zone";
Deletions:
zone "ing" in {
file "ing.zone";
zone "micro" in {
file "micro.zone";

Revision [3654]

Edited on 2015-11-16 13:00:17 by JeffTaylor [Updated T1 IP addresses]
Additions:
45.56.115.189; # ns0.opennic.glue
45.56.116.224; # ns0.opennic.glue
198.46.244.109; # ns3.opennic.glue
178.63.145.230; # ns4.opennic.glue
2a01:4f8:101:3062::5:2; # ns4.opennic.glue
94.103.153.176; # ns5.opennic.glue
2a02:990:219:1:ba:1337:cafe:3; # ns5.opennic.glue
45.79.192.100; # ns7.opennic.glue
2600:3c02::f03c:91ff:fec8:d863; # ns7.opennic.glue
188.226.215.149; # ns9.opennic.glue
2a03:b0c0:0:1010::48:4001; # ns9.opennic.glue
188.226.146.136; # ns10.opennic.glue
Deletions:
75.127.96.89; # ns0.opennic.glue
185.19.105.30; # ns1.opennic.glue
198.136.57.121; # ns3.opennic.glue
84.200.228.200; # ns4.opennic.glue
23.98.70.54; # ns5.opennic.glue
66.244.95.11; # ns7.opennic.glue
2001:470:1f10:c6::11; # ns7.opennic.glue
209.141.35.9; # ns9.opennic.glue
2607:f358:1:fed5:22:4329:2793:fc94; # ns9.opennic.glue

Revision [3586]

Edited on 2015-06-01 15:07:01 by JeffTaylor [add allow-query options]
Additions:
Finally, you will want to consider WHO is allowed to query your server and add an appropriate line to your options file. The default behavior (if you have not specified otherwise) is to only allow your local network to query, and the line for your options file would look like this:
%%allow-recursion { localnets; localhost; };%%
However if you wish to allow anyone from the internet to query your server, you would use this option:
%%allow-recursion { any; };%%

Revision [3174]

Edited on 2014-05-09 20:44:58 by Nesa [updated ns10 ip]
Additions:
50.116.19.70; # ns10.opennic.glue
Deletions:
103.4.16.80; # ns10.opennic.glue

Revision [3173]

Edited on 2014-05-02 21:30:49 by Nesa [updated ns5 IP]
Additions:
23.98.70.54; # ns5.opennic.glue
Deletions:
173.208.225.19; # ns5.opennic.glue

Revision [3172]

Edited on 2014-04-27 07:16:44 by Nesa [Forgot the ipv6]
Additions:
2001:470:f032:10:0:100:53:10; # ns2.opennic.glue
Deletions:
2001:470:8388:10:0:100:53:10; # ns2.opennic.glue

Revision [3171]

Edited on 2014-04-27 07:09:44 by Nesa [changed NS2 ip to 173.160.58.202;]
Additions:
173.160.58.202; # ns2.opennic.glue
Deletions:
216.87.84.210; # ns2.opennic.glue

Revision [3135]

Edited on 2013-11-19 18:12:53 by JeffTaylor [Updated T1 server list]
Additions:
185.19.105.30; # ns1.opennic.glue
216.87.84.210; # ns2.opennic.glue
2001:470:8388:10:0:100:53:10; # ns2.opennic.glue
198.136.57.121; # ns3.opennic.glue
2001:470:8269::53; # ns3.opennic.glue
84.200.228.200; # ns4.opennic.glue
173.208.225.19; # ns5.opennic.glue
207.192.71.13; # ns6.opennic.glue
2002:cfc0:470d::1; # ns6.opennic.glue
66.244.95.11; # ns7.opennic.glue
2001:470:1f10:c6::11; # ns7.opennic.glue
178.63.116.152; # ns8.opennic.glue
2a01:4f8:141:4281::999; # ns8.opennic.glue
209.141.35.9; # ns9.opennic.glue
2607:f358:1:fed5:22:4329:2793:fc94; # ns9.opennic.glue
103.4.16.80; # ns10.opennic.glue
Note the 'masters' sections which allows you to specify all of the available tier-1 servers in a single block. This simplifies making updates when needed. OpenNIC peers will typically carry their own root zone, but otherwise provides all other OpenNIC zones.
Deletions:
216.87.84.210; # ns2.opennic.glue.
2001:470:8388:10:0:100:53:10; # ns2.opennic.glue.
198.136.57.121; # ns3.opennic.glue.
2001:470:8269::53; # ns3.opennic.glue.
173.208.225.19; # ns5.opennic.glue.
207.192.71.13; # ns6.opennic.glue.
2002:cfc0:470d::1; # ns6.opennic.glue.
66.244.95.11; # ns7.opennic.glue.
2001:470:1f10:c6::11; # ns7.opennic.glue.
178.63.116.152; # ns8.opennic.glue.
2a01:4f8:141:4281::999; # ns8.opennic.glue.
209.141.35.9; # ns9.opennic.glue.
2607:f358:1:fed5:22:4329:2793:fc94; # ns9.opennic.glue.
103.4.16.80; # ns10.opennic.glue.
202.83.95.229; # ns21.opennic.glue.
84.200.228.200; # ns4.opennic.glue.
Note the 'masters' sections which allows you to specify all of the available tier-1 servers in a single block. This simplifies making updates when needed. NS4 is a peer which carries a different root zone, but otherwise provides all other OpenNIC zones.

Revision [3003]

Edited on 2013-06-06 18:38:15 by JeffTaylor [Updated IP for NS10]
Additions:
103.4.16.80; # ns10.opennic.glue.
Deletions:
103.1.185.92; # ns10.opennic.glue.

Revision [2968]

Edited on 2013-01-15 04:50:32 by JeffTaylor [Updated IP for NS10]
Additions:
~- Do not include the root zone or hints
~- Do include slave zones for all of the OpenNIC TLDs
~- Add 127.0.0.1 as the first nameserver in resolv.conf
Deletions:
* Do not include the root zone or hints
* Do include slave zones for all of the OpenNIC TLDs
* Add 127.0.0.1 as the first nameserver in resolv.conf

Revision [2967]

Edited on 2013-01-15 04:49:35 by JeffTaylor [Alt config info added]
Additions:
=== Alternate Configurations ===
A standard configuration will provide full nameserver capabilities, however in certain cases you may wish to modify the configuration below. As an example, if you are setting up a server within a company or school campus which already has their own nameservers providing DNS information for locating on-site computers. To allow both on-site and OpenNIC name resolution, try the following:
* Do not include the root zone or hints
* Do include slave zones for all of the OpenNIC TLDs
* Add 127.0.0.1 as the first nameserver in resolv.conf
This solution should allow your server to ONLY resolve OpenNIC domains, then pass resolution of everything else back to your network.

Revision [2966]

The oldest known version of this page was created on 2013-01-15 04:31:53 by JeffTaylor [Alt config info added]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki