Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
opennic:t2slaved [2020-04-11T17:09:03Z] – only ";" in direcction Otopus | opennic:t2slaved [2022-11-26T21:04:58Z] – Typos all over the place sry Olde16 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Slaved Zones with BIND9 ====== | ====== Slaved Zones with BIND9 ====== | ||
+ | |||
+ | Also refer to [[opennic: | ||
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' | 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' | ||
- | 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 [[mailinglist|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: |
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 29: | Line 31: | ||
# check to make sure these are still correct! | # check to make sure these are still correct! | ||
masters opennicNS { | masters opennicNS { | ||
- | | + | |
- | 2001: | + | 2001: |
- | 104.168.144.17; | + | 104.168.144.17; |
- | 2001: | + | 2001: |
- | 163.172.168.171; | + | 163.172.168.171; |
- | 2001: | + | 2001: |
- | 94.103.153.176; | + | 94.103.153.176; |
- | 2001: | + | 2001: |
- | 207.192.71.13; | + | 207.192.71.13; |
- | 178.63.116.152; | + | 178.63.116.152; |
- | 2a01: | + | 2a01: |
- | 138.68.128.160; | + | 138.68.128.160; |
- | 2a03: | + | 2a03: |
- | 188.226.146.136; | + | 188.226.146.136; |
- | 2001: | + | 2001: |
- | 45.55.97.204; | + | 45.55.97.204; |
- | 2604: | + | 2604: |
- | 79.124.7.81; | + | 79.124.7.81; |
- | 2a01: | + | 2a01: |
}; | }; | ||
masters opennicPeers { | masters opennicPeers { | ||
Line 80: | Line 82: | ||
type slave; | type slave; | ||
file " | file " | ||
- | allow-transfer { any; }; | ||
- | notify yes; | ||
- | masters { opennicNS; opennicPeers; | ||
- | }; | ||
- | zone " | ||
- | type slave; | ||
- | file " | ||
allow-transfer { any; }; | allow-transfer { any; }; | ||
notify yes; | notify yes; | ||
Line 199: | Line 194: | ||
type slave; | type slave; | ||
file " | file " | ||
+ | allow-transfer { any; }; | ||
+ | notify yes; | ||
+ | masters { opennicNS; opennicPeers; | ||
+ | }; | ||
+ | zone " | ||
+ | type slave; | ||
+ | file " | ||
allow-transfer { any; }; | allow-transfer { any; }; | ||
notify yes; | notify yes; | ||
Line 219: | Line 221: | ||
To finish your new configuration, | To finish your new configuration, | ||
- | 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 | + | **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 | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ----------------Historical Note---------------------- | ||
+ | // The old test link http:// | ||
===== Alternate Configurations ===== | ===== Alternate Configurations ===== | ||