Homepage INAIC    
   
   
Tools & Software

Link to the official TLD Registrars TLD Registrars
Link to Global TLD Whois Global TLD Whois
Link to the Public-Root Root-Servers Public-Root Servers
Link to the Public Internet Service Providers Public ISPs
Link to Link to TLD-News TLD-News
Link to the Public-Discussions List TLD Discussion List
Link to Tools and Software Tools and Software
Link to Uniform Corporate Domain Authority UCDA
Link to the International Security Agency Multilingual TLDs
Link to the INAIC Volunteers The INAIC Volunteers
Link to Frequently Asked Questions FAQ
Link to Technical Support Technical Support
Link to contact the Internet Names Authorization & Information Center (INAIC) Contact
Next Section
Upgrade Unix/Linux Name Servers using Cache.
These instructions will guide Unix system administrators in making changes to their domain name server cache. (Hint file) This file holds the information on root name servers needed to initialize the cache of Internet domain name servers. Once the changes are complete your system will resolve the Public-Root and the Next Generation Internet.
     
 
arrow1arrow   Login to your Unix system as the root administrator. You must be logged in as root for these changes to take effect.
   
arrow2arrow   Use your favorite editor or text viewer to display the file /etc/named.conf. If you can't find that file check for one named /etc/named.boot. The file /etc/named.conf is used by BIND versions 8 and 9. If you have /etc/named.boot then you are most likely running BIND version 4 and you should consider upgrading your name server.
 
arrow3arrow   If your running a BIND 4 your /etc/named.boot should look something like this:

; /etc/named.boot
;
directory /usr/local/adm/named
; type domain source host/file backup file
cache . root.cache
secondary Berkeley.EDU 128.32.137.8 ucbhosts.bak
secondary 32.128.IN-ADDR.ARPA 128.32.137.8 ucbhosts.rev.bak
primary 0.0.127.IN-ADDR.ARPA localhost.rev

 
arrow4arrow   If your running BIND 8 or 9 your /etc/named.conf should look something like this:

options {
directory "/usr/local/adm/named"
};

zone "." {
type hint;
file "root.cache"
};

zone "localhost" {
type master;
file "pri/localhost"
};

 
arrow5arrow   In both cases the root.cache is the name of the cache file and it is located at the directory /usr/local/adm/named.

Your root cache file should look something like this:

.. 3600000 IN NS
a.public-root.com.
a.public-root.com. 3600000 A 57.67.193.189
;
.. 3600000 NS
b.public-root.com.
b.public-root.com. 3600000 A 61.9.136.52
;
.. 3600000 NS
c.public-root.com.
c.public-root.com. 3600000 A 68.255.182.111
;
.. 3600000 NS
e.public-root.com.
e.public-root.com. 3600000 A 216.138.219.83
;
.. 3600000 NS
f.public-root.com.
f.public-root.com. 3600000 A 66.15.174.197
;
.. 3600000 NS
g.public-root.com.
g.public-root.com. 3600000 A 199.5.157.131
;
.. 3600000 NS
h.public-root.com.
h.public-root.com. 3600000 A 65.118.74.205
;
.. 3600000 NS
i.public-root.com.
i.public-root.com. 3600000 A 203.187.202.205
;
.. 3600000 NS
j.public-root.com.
j.public-root.com. 3600000 A 203.199.124.188
;
.. 3600000 NS
m.public-root.com.
m.public-root.com. 3600000 A 212.97.45.51

 
arrow6arrow   Using the information obtained earlier from your named.boot or named.conf file, change to the default directory location which contains the cache file. In our case this directory is located at /usr/local/adm/named. Then backup your cache by entering the following commands at your linux prompt;

prompt:~$ cd /usr/local/adm/named
prompt:~$ cp root.cache root.cache.backup

Creating a backup copy of your root.cache file will allow you to restore your original configuration if required.

 
 
arrow7arrow   Initiate an fetch to http://public-root.net/hint.txt and pickup a replacement cache file. Save that file as your new root.cache.
   
arrow8arrow  

Now you have to configure your unix resolver /etc/resolv.conf.

Issue the following command at your Unix prompt:

prompt:~$ cp /etc/resolv.conf /etc/resolv.conf.backup

This will create a backup copy of your /etc/resolv.conf file. In the event you want to later restore your original configuration that information will be stored in the /etc/resolv.conf.backup file.

   
arrow9arrow   Use a line editor like vi or pico to edit your /etc/resolv.conf file. It should look something like this:

# /etc/resolv.conf
# Our domain
domain inaic.org
#
# Our nameservers
nameserver 127.0.0.1
nameserver 192.0.2.111
nameserver 192.168.173.10

Make sure the first nameserver field points to the IPv4 address 127.0.0.1. This is the localhost address where your nameserver is running.

   
arrow10arrow Replace the remaining nameserver fields with the IPv4 addresses of the Public-Root domain name servers. Use servers from our list that are closest to your geographical region.
   
arrow11arrow   Save the changes you made to /etc/resolv.conf and restart your nameserver by entering the command /usr/sbin/ndc restart or reboot your server.
 
arrow12arrow   Welcome, you are now resolving the Public-Root system. Click here to test your configuration.
 
 
The Tools & Software section is updated frequently.
 
     

Next Section
Next Section

INAIC | UN1D | TLD.NAME | Public-Root | UCDA
 
  * The INAIC is the representative body for the next generation Internet DNS system globally supported by Public-Root, UN1D, TLD.NAME, UCDA, and many more.
Copyright ©2004 - 2015 by the Internet Names Authorization & Information Center (INAIC). All rights reserved.