This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revisionBoth sides next revision |
| playground:overview [2018-11-20T19:06:54Z] – [See also] s4 | playground:overview [2018-11-20T19:07:58Z] – [OpenNIC] s4 |
|---|
| Worldwide Anycast: | Worldwide Anycast: |
| |
| 185.121.177.177 | * 185.121.177.177 |
| 169.239.202.202 | * 169.239.202.202 |
| 2a05:dfc7:5::53 | * 2a05:dfc7:5::53 |
| 2a05:dfc7:5::5353 | * 2a05:dfc7:5::5353 |
| |
| To avoid responsiveness problems, follow RFC-7706: [https://www.heise.de/netze/rfc/rfcs/rfc7706.shtml#page-9 root zone transfer made simple - serve root@home] edit an appropriate /etc/named.conf with ''.libre'' domains etc. being transferred (see OpenNIC [https://wiki.opennic.org/start wiki] for details) , restart [[BIND]] and no longer suffer unresponsive OpenNIC servers during [[Domain name resolution]]. Do a zone transfer just like the full tier 2 servers do as [https://wiki.opennic.org/opennic/tier2setup described] in the OpenNIC wiki. | To avoid responsiveness problems, follow RFC-7706: [https://www.heise.de/netze/rfc/rfcs/rfc7706.shtml#page-9 root zone transfer made simple - serve root@home] edit an appropriate /etc/named.conf with ''.libre'' domains etc. being transferred (see OpenNIC [https://wiki.opennic.org/start wiki] for details) , restart [[BIND]] and no longer suffer unresponsive OpenNIC servers during [[Domain name resolution]]. Do a zone transfer just like the full tier 2 servers do as [https://wiki.opennic.org/opennic/tier2setup described] in the OpenNIC wiki. |