Solved

DNS on Solaris 2.6

Posted on 2000-04-17
4
257 Views
Last Modified: 2013-12-23
probably simple for you but not for me....

Can someone help me with the basic DNS configuration on Solaris 2.6.
I would like to install a DNS server that would resolve the internal names by itslef but resolve internet names (outside) from our main DNS server.

I would like step by step procedure to configure this server. This server is currently using existing DNS server to resolve the names.
0
Comment
Question by:wallstreetx
  • 2
4 Comments
 
LVL 40

Expert Comment

by:jlevie
ID: 2739468
What you need to do is to set up an caching secondary server. My recommendation would be to install the latest bind (8.2.2 patchlevel5) instead of using Sun's in.named for security reasons. I can tell you how to set up a caching DNS with Sun's in.named or with bind, but I need to know which you will use.
0
 

Author Comment

by:wallstreetx
ID: 2744410
I was looking at BIND and have never configured/installed it but seems it is complicated to install plus I don't have any compiler installed on the machine. It might be easier to use Sun's in.named.

Thanks
0
 
LVL 40

Expert Comment

by:jlevie
ID: 2744552
There are several files that need to be set up. It's going to be a pain to extract them from one of these comment boxes, so if you'll send an email to jlevie@bellsouth.net I'll send you a tar file that has all the pieces. You'll need to do some minor edits on them to suit your network.
0
 

Accepted Solution

by:
nnnppp earned 200 total points
ID: 2799396
Hi. Wallstreetx.

you can do it If your machine currently is only a client of existing DNS server.

1. DNS server setup on your machine.
  1.1 Check if the machine is useing DNS.
     -  login as superuser.
     -  check/edit the /etc/nsswitch.conf file and add "dns" at entry of hosts, as follow:
           hosts:      files dns
     -  save the file.
  1.2 Setting up this machine as a proper DNS client.
     -  editing the /etc/resolv.conf file as follow.
        domain yourdomainname
        nameserver 127.0.0.1
        nameserver IP-for-your-main-DNS-server
        nameserver IP-for-outside-DNS-server      ; optional
      ; End of File
     - save and exit the file.
  1.3 Setting up the boot file.
     -  Creating the /etc/named.boot file as follow.
        ;
        ; files required by in.named are located here
        directory /var/named
        ; here are the names of the primary files
        cache      .                              named.ca
        primary    yourdomainname                 mydomain.db
        primary    0.0.127.in-addr.arpa           named.local
        primary    6.45.123.in-addr.arpa          mydomain.db.rev ; assume you have 123.45.6 as
                                                                  ; your zone's IP-address.
      ; End of File
      - save and exit the file.
  1.4 Setting up the named.ca file.
      -  If your network is connected to the Internet now, at the present time you obtain your named.ca
         file from InterNIC registration services via:

          Anonymous FTP. The FTP site is: ftp.rs.internic.net. The file name is: /domain/named.root.

          Gopher. The Gopher site is: rs.internic.net. The file is: named.root, which can be
          found under the InterNIC Registration Services menu, InterNIC Registration Archives submenu.

      -  If you are following the naming conventions used in this solution, you then move named.root
         to /var/named/named.ca.
         
      -  following is a example Internet named.ca file:
     
            ;       This file holds the information on root name servers needed to
            ;       initialize cache of Internet domain name servers
      ;       (e.g. reference this file in the "cache  .  <file>"
      ;       configuration file of BIND domain name servers).
      ;
      ;       This file is made available by InterNIC registration services
      ;       under anonymous FTP as
      ;           file                /domain/named.root
      ;           on server           FTP.RS.INTERNIC.NET
      ;       -OR- under Gopher at    RS.INTERNIC.NET
      ;           under menu          InterNIC Registration Services (NSI)
      ;              submenu          InterNIC Registration Archives
      ;           file                named.root
      ;
      ;       last update:    Aug 22, 1997
      ;       related version of root zone:   1997082200
      ;
      ;
      ; formerly NS.INTERNIC.NET
      ;
      .                        3600000  IN  NS    A.ROOT-SERVERS.NET.
      A.ROOT-SERVERS.NET.      3600000      A     198.41.0.4
      ;
      ; formerly NS1.ISI.EDU
      ;
      .                        3600000      NS    B.ROOT-SERVERS.NET.
      B.ROOT-SERVERS.NET.      3600000      A     128.9.0.107
      ;
      ; formerly C.PSI.NET
      ;
      .                        3600000      NS    C.ROOT-SERVERS.NET.
      C.ROOT-SERVERS.NET.      3600000      A     192.33.4.12
      ;
      ; formerly TERP.UMD.EDU
      ;
      .                        3600000      NS    D.ROOT-SERVERS.NET.
      D.ROOT-SERVERS.NET.      3600000      A     128.8.10.90
      ;
      ; formerly NS.NASA.GOV
      ;
      .                        3600000      NS    E.ROOT-SERVERS.NET.
      E.ROOT-SERVERS.NET.      3600000      A     192.203.230.10
      ;
      ; formerly NS.ISC.ORG
      ;
      .                        3600000      NS    F.ROOT-SERVERS.NET.
      F.ROOT-SERVERS.NET.      3600000      A     192.5.5.241
      ;
      ; formerly NS.NIC.DDN.MIL
      ;
      .                        3600000      NS    G.ROOT-SERVERS.NET.
      G.ROOT-SERVERS.NET.      3600000      A     192.112.36.4
      ;
      ; formerly AOS.ARL.ARMY.MIL
      ;
      .                        3600000      NS    H.ROOT-SERVERS.NET.
      H.ROOT-SERVERS.NET.      3600000      A     128.63.2.53
      ;
      ; formerly NIC.NORDU.NET
      ;
      .                        3600000      NS    I.ROOT-SERVERS.NET.
      I.ROOT-SERVERS.NET.      3600000      A     192.36.148.17
      ;
      ; temporarily housed at NSI (InterNIC)
      ;
      .                        3600000      NS    J.ROOT-SERVERS.NET.
      J.ROOT-SERVERS.NET.      3600000      A     198.41.0.10
      ;
      ; housed in LINX, operated by RIPE NCC
      ;
      .                        3600000      NS    K.ROOT-SERVERS.NET.
      K.ROOT-SERVERS.NET.      3600000      A     193.0.14.129
      ;
      ; temporarily housed at ISI (IANA)
      ;
      .                        3600000      NS    L.ROOT-SERVERS.NET.
      L.ROOT-SERVERS.NET.      3600000      A     198.32.64.12
      ;
      ; housed in Japan, operated by WIDE
      ;
      .                        3600000      NS    M.ROOT-SERVERS.NET.
      M.ROOT-SERVERS.NET.      3600000      A     202.12.27.33
      ; End of File


  1.5  Setting up the mydomain.db file which contains all the data about every machine in your zone.
     - editing /var/named/mydomain.db:
           ;
       ;
      yourdomainname  IN SOA thismachine.yourdomainname root.thismachine.yourdomainname (
                  2000051101       ;  serial number (YYYYMMDD##)
                       10800       ;  refresh every 3 hours
                       10800       ;  retry every 3 hours
                       604800      ;  expire after a week
                       86400 )     ;  TTL of 1 day
       ; Name Servers
       yourdomainname            IN  NS  thismachine.yourdomainname
       ; Addresses
       localhost                 IN  A  127.0.0.1
       thismachine               IN  A  123.45.6.1      ; assume this machine has this IP-address
       machine1                  IN  A  123.45.6.11      ; assume your local machines has IP-address
       machine2                  IN  A  123.45.6.20      ; 11, 20, 21 ...
       machine3                  IN  A  123.45.6.21
            .
            .
            .
       ; End of File
 
   1.6  Setting up the mydomain.db.rev file.
       ;
      ;
      6.45.123.in-addr.arpa.  IN SOA thismachine.yourdomainname root.thismachine.yourdomainname (
                  2000051101       ;  serial number (YYYYMMDD##)
                       10800       ;  refresh every 3 hours
                       10800       ;  retry every 3 hours
                       604800      ;  expire after a week
                       86400 )     ;  TTL of 1 day
      ;
       6.45.123.in-addr.arpa.   IN  NS  thismachine.yourdomainname.
       1                        IN  PTR thismachine.yourdomainname.
       11                       IN  PTR machine1.yourdomainname.
       20                       IN  PTR machine2.yourdomainname.
       21                       IN  PTR machine3.yourdomainname.
           .
           .
           .
       ;
       ; End of File
       
 
   1.7  Setting up the named.local file
        ;
        0.0.127.in-addr.arpa. IN SOA  thismachine.yourdomainname root.thismachine.yourdomainname (
                      20000511001           ;  serial number (YYYYMMDD##)            
                            10800           ;  refresh every 3 hours
                            10800           ;  retry every 3 hours
                            604800          ;  expire after a week
                            86400 )         ;  TTL of 1 day
       ; Name Servers
       0.0.127.in-addr.arpa.      IN  NS   thismachine.yourdomainname
       1                          IN  PTR  localhost.
       ;
       ; End of File
       
   1.8  reooot this machine.
   
2. DNS client setup for the machines in your zone.
  1.1 Check if the machines are useing DNS.
     -  login as superuser.
     -  check/edit the /etc/nsswitch.conf file and add "dns" at entry of hosts, as follow:
           hosts:      files dns
     -  save the file.
  1.2 Setting up these machine as a proper DNS client.
     -  editing the /etc/resolv.conf file of each machine.
        domain yourdomainname
        nameserver 123.45.6.1
        nameserver IP-for-your-main-DNS-server
        nameserver IP-for-outside-DNS-server      ; optional
      ; End of File
     - save and exit the file.
  1.3  reboot
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Attention: This article will no longer be maintained. If you have any questions, please feel free to mail me. jgh@FreeBSD.org Please see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/ for the updated article. It is avail…
This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now