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:t2slaved [2017-09-09T10:29:14Z]
edoardo Re- added "o" zone
opennic:t2slaved [2020-11-27T01:49:44Z]
haloXenO We don't serve bit-domain anymore.
Line 3: Line 3:
 FIXME This guide was copied directly from the old wiki. It likely needs some updates for the latest BIND software and OpenNIC configuration. If this guide doesn't work, try using the [[opennic:srvzone|srvzone script]]. FIXME This guide was copied directly from the old wiki. It likely needs some updates for the latest BIND software and OpenNIC configuration. If this guide doesn't work, try using the [[opennic:srvzone|srvzone script]].
  
-For those wishing to set up a more robust local nameserver, or if you plan on running a public [[tier1|Tier 1]] or [[tier2|Tier 2]] server for OpenNIC, configuring BIND with slave zones is the preferred method. Please read the 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.+For those wishing to set up a more robust local nameserver, or if you plan on running a public [[tier1|Tier 1]] or [[tier2|Tier 2]] server for OpenNIC, configuring BIND with slave zones is the preferred method. Please read [[opennic:operatorpolicies|the policies]] before running a public T2 server. You should also join the appropriate [[mailinglist|MailingLists]] so you'll be notified of changing situations which may affect your operation.
  
 Slave zones contain the full record of domain names for each OpenNIC TLD. When a query is made for an OpenNIC domain, you have the exact information needed to proceed directly to that domain, thus eliminating several hops in processing a query. Note that the only difference between a Tier 1 and Tier 2 server is that Tier 1 servers do not process public queries for ICANN domains - they ONLY process OpenNIC TLD requests. Slave zones contain the full record of domain names for each OpenNIC TLD. When a query is made for an OpenNIC domain, you have the exact information needed to proceed directly to that domain, thus eliminating several hops in processing a query. Note that the only difference between a Tier 1 and Tier 2 server is that Tier 1 servers do not process public queries for ICANN domains - they ONLY process OpenNIC TLD requests.
Line 27: Line 27:
  
 <file> <file>
 +# check to make sure these are still correct!
 masters opennicNS { masters opennicNS {
- 45.56.115.189; # ns0.opennic.glue +        161.97.219.84;                  # ns2.opennic.glue 
- 45.56.116.224; # ns0.opennic.glue +        2001:470:4212:10:0:100:53:10;   # ns2.opennic.glue 
- 161.97.219.84; # ns2.opennic.glue +        104.168.144.17;                 # ns3.opennic.glue 
- 2001:470:4212:10:0:100:53:10; # ns2.opennic.glue +        2001:470:8269::53;              # ns3.opennic.glue 
- 104.168.144.17; # ns3.opennic.glue +        163.172.168.171               # ns4.opennic.glue 
- 2001:470:8269::53; # ns3.opennic.glue +        2001:bc8:4400:2100::17:213    # ns4.opennic.glue 
- 178.63.145.230; # ns4.opennic.glue +        94.103.153.176;                 # ns5.opennic.glue 
- 2a01:4f8:101:3062::5:2; # ns4.opennic.glue +        2001:bc8:4400:2100::17:213    # ns5.opennic.glue 
- 94.103.153.176; # ns5.opennic.glue +        207.192.71.13;                  # ns6.opennic.glue 
- 2a02:990:219:1:ba:1337:cafe:3; # ns5.opennic.glue +        178.63.116.152;                 # ns8.opennic.glue 
- 207.192.71.13; # ns6.opennic.glue +        2a01:4f8:141:4281::999;         # ns8.opennic.glud 
- 2002:cfc0:470d::1; # ns6.opennic.glue +        138.68.128.160;                 # ns9.opennic.glue 
- 178.63.116.152; # ns8.opennic.glue +        2a03:b0c0:1:a1::46b:a001;       # ns9.opennic.glue 
- 2a01:4f8:141:4281::999; # ns8.opennic.glue +        188.226.146.136;                # ns10.opennic.glue 
- 138.68.128.160; # ns9.opennic.glue +        2001:470:1f04:ebf::2;           # ns10.opennic.glue 
- 2a03:b0c0:1:a1::46b:a001; # ns9.opennic.glue +        45.55.97.204                  # ns11.opennic.glue 
- 188.226.146.136; # ns10.opennic.glue +        2604:a880:800:a1::14c1:1;       # ns11.opennic.glue 
- 2001:470:1f04:ebf::2; # ns10.opennic.glue +        79.124.7.81;                    # ns12.opennic.glue 
- 138.197.44.179; # ns11.opennic.glue+        2a01:8740:1:ff13::ae67;         # ns12.opennic.glue
 }; };
 masters opennicPeers { masters opennicPeers {
Line 79: Line 80:
  type slave;  type slave;
  file "bbs.zone";  file "bbs.zone";
- allow-transfer { any; }; 
- notify yes; 
- masters { opennicNS; opennicPeers; }; 
-}; 
-zone "bit" in { 
- type slave; 
- file "bit.zone"; 
  allow-transfer { any; };  allow-transfer { any; };
  notify yes;  notify yes;
Line 135: Line 129:
  type slave;  type slave;
  file "indy.zone";  file "indy.zone";
 + allow-transfer { any; };
 + notify yes;
 + masters { opennicNS; opennicPeers; };
 +};
 +zone "libre" in {
 + type slave;
 + file "libre.zone";
  allow-transfer { any; };  allow-transfer { any; };
  notify yes;  notify yes;
Line 191: Line 192:
  type slave;  type slave;
  file "o.zone";  file "o.zone";
 + allow-transfer { any; };
 + notify yes;
 + masters { opennicNS; opennicPeers; };
 +};
 +zone "epic" in {
 + type slave;
 + file "epic.zone";
  allow-transfer { any; };  allow-transfer { any; };
  notify yes;  notify yes;
Line 211: Line 219:
 To finish your new configuration, restart BIND. If you have logging enabled, you should see BIND attempting to transfer the various zones to your server. If you look in the directory specified in the options file (or in the directory you specified if full path names were used), you should see the zone files being added. To finish your new configuration, restart BIND. If you have logging enabled, you should see BIND attempting to transfer the various zones to your server. If you look in the directory specified in the options file (or in the directory you specified if full path names were used), you should see the zone files being added.
  
-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.+**TESTING T2 Public Server** 
 + 
 +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 the test link  [[https://servers.opennicproject.org/srvtest3/]] and entering your IP address. If there are any failures you cannot resolve, please visit the mailing list or IRC to get help. 
 + 
 + 
 + 
 + 
 + 
 +----------------Historical Note----------------------
  
 + // The old test link http://report.opennicproject.org/t2log/t2.php does not always produce favorable results//
 ===== Alternate Configurations ===== ===== Alternate Configurations =====
  
  • /wiki/data/pages/opennic/t2slaved.txt
  • Last modified: 5 months ago
  • by haloXenO