Differences

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

Link to this comparison view

Next revision
Previous revision
opennic:t2hints [2017-04-19T02:09:08Z]
jonaharagon created
opennic:t2hints [2020-06-21T19:52:13Z]
Eleix Fix IP reference for root hints, and opennicproject.org domain ip address longer matches the address with the glue records.
Line 3: Line 3:
 The easiest setup is to use a local caching server. The following will configure a private nameserver for your personal use.  The easiest setup is to use a local caching server. The following will configure a private nameserver for your personal use. 
  
-:!: If you wish to run a public Tier 2 server, follow [[http://​wiki.opennic.org/​opennic:​tier2setup#​slave_zone_method_bind|the Slaved Zones instructions]],​ not these.+:!: If you wish to run a public ​[[tier2|Tier 2]] server, follow [[http://​wiki.opennic.org/​opennic:​tier2setup#​slave_zone_method_bind|the Slaved Zones instructions]],​ not these.
  
 If you are trying to anonymize your browsing history, please be aware that installing your own nameserver or using OpenNIC services will not hide your queries. OpenNIC operators are only in control of OpenNIC domains. Any queries you make to ICANN domains will still be processed by ICANN servers. However, configuring your own nameserver does give you more control over the processing of your queries, and can bypass any modifications your ISP may make to those lookups. If you are trying to anonymize your browsing history, please be aware that installing your own nameserver or using OpenNIC services will not hide your queries. OpenNIC operators are only in control of OpenNIC domains. Any queries you make to ICANN domains will still be processed by ICANN servers. However, configuring your own nameserver does give you more control over the processing of your queries, and can bypass any modifications your ISP may make to those lookups.
Line 18: Line 18:
 Make note of the filename, in this case "/​etc/​bind/​db.root"​. This is your root hints file, which instructs BIND where to go to find '​hints'​ about the location of each TLD. The default file will direct you to the standard ICANN root servers. We want to replace this with a hints file that instead queries OpenNIC servers: Make note of the filename, in this case "/​etc/​bind/​db.root"​. This is your root hints file, which instructs BIND where to go to find '​hints'​ about the location of each TLD. The default file will direct you to the standard ICANN root servers. We want to replace this with a hints file that instead queries OpenNIC servers:
  
-  dig . NS @75.127.96.89 > /​etc/​bind/​db.root+  dig . NS @45.56.115.189 > /​etc/​bind/​db.root
  
 If you wish to ensure this file stays up to date, you could set up a cron job to perform the above command periodically. Note that the servers listed in this file are not expected to change frequently. If you wish to ensure this file stays up to date, you could set up a cron job to perform the above command periodically. Note that the servers listed in this file are not expected to change frequently.
Line 34: Line 34:
   ping opennic.glue   ping opennic.glue
  
-This should resolve to 75.127.96.89, the same as opennicproject.org. If you cannot resolve opennic.glue,​ verify that BIND has been started successfully.+This should resolve to 45.56.115.189 or 45.56.116.224. If you cannot resolve opennic.glue,​ verify that BIND has been started successfully.
  • /wiki/data/pages/opennic/t2hints.txt
  • Last modified: 7 weeks ago
  • by Eleix