Sponsored Content
Operating Systems Solaris configure DNS server on solaris Post 302099221 by Tornado on Sunday 10th of December 2006 05:15:40 PM
Old 12-10-2006
I just tried to download it now... It worked fine.
Try to download it again.

Here is the named.conf template file from the download.
Code:
//
//james liu 2/23/96
//revised 3/23/2000
//
//dns configuration file compatible with solaris 2.7 and later. This
//configuration is targeted at primary and secondary dns server setups.
//
//for solaris 2.6 and earlier, do not edit this file, but
//see the "named.boot" file for instructions.
//
//installation instructions:
//
//we assume you've unpacked this distribution.
//
//step 1;
//-------
//edit named.conf, named.local, named.cache, named.mydomain, and
//named.domain.rev and globally change all instances of "myhost" to
//the actual hostname, and "mydomain" to the desired domain name.
//also, change the ip numbers for the domain to match those for your
//network. for the reverse domain, just reverse the numbers for the
//class of address. this template is designed for a single class c.
//
//step 2:
//-------
//to use this, and create a symbolic link to this in /etc filesystem
//link to this file: ie:
//
//# ln -s [path-to-this]/named.conf /etc/named.conf
//
//step 3:
//-------
//start the dns server. /usr/sbin/in.named.
//
//
//
//for secondary domain name servers, use these entries; format is:
//<dns type> <domain> <prim. ip(s)> <filename>
//note, you can spec more than one prim. ip to download from
//in addition, the filename is the name to store the map in. you don't
//have to create this file. the common practice is to assign filenames
//as *.bak for files this server caches as a secondary dns relative to
//some other dns primary.
//
//almost all dns's can use themselves to resolve the local host
//you usually will leave this entry alone
//
//all dns's need to spec top-level cache servers that resolve world internet
//hostnames. there can be one or more entries and are spec'd in the cache
//file.
//
//if you are a subnet as a part of a larger network, (e.g. your domain is
//"mysubnet.mydomain.com", you may want to set forwarding to a higher
//level server (the one that serves names for "mydomain.com". if so,
//uncomment the 'forwarders' line below and edit it for your network
//parameters.
//

//specify the directory prefix where you plan to store the dns map files.
//the default here is /var/named.
options {
 	directory	 "/var/named";
//
//uncomment if you want to send queries outside of the primary to a
//a forwarders server.
//	forwarders       {
//		129.150.254.2;
//	};
};

//choose between primary or being a secondary server. a secondary dns is
//simply a server that downloads the dns maps from some other primary or
//secondary. the default here is to be a primary and have only one
//class c subnet. the dns needs a "forward map" that looks up ip address
//for a given hostname, and a "reverse map" that looks up hostname for
//a given ip address. if you have multiple subnets and domain name spaces,
//you should have multiple forward maps, and/or multiple reverse maps.
//in many networks, there is a single domain name space that spans several
//subnets, in which case, there will be one forward map, and many reverse
//maps.

zone "mydomain.com" in {
	type master;
	file "named.mydomain";
};

add more zones if you have multiple subnets as primary

zone "9.200.129.in-addr.arpa" in {
	type master;
	file "named.mydomain.rev";
};
//
//you can make this a secondary rather than primary by uncommenting
//these lines and commenting out the above primary zones and replacing
//with these below.  The masters IP address(es) are set to whatever your
//masters are.
//zone "mydomain.com" in {
//        type slave;
//        file "named.mydomain.bak";
//        masters { 129.200.9.1; 129.200.9.2 };
//};

//zone "9.200.129.in-addr.arpa" in {
//        type slave;
//        file "named.mydomain.9.bak";
//        masters { 129.200.9.1; 129.200.10.1 };
//};

//zone "10.200.129.in-addr.arpa" in {
//        type slave;
//        file "named.mydomain.10.bak";
//        masters { 129.200.10.1; 129.200.9.1 };
//};

// don't usually need to mess with this entry. You may need to edit
// the map file, named.local, however.
zone "0.0.127.in-addr.arpa" in {
	type master;
	file "named.local";
};

// nothing to do here.
zone "." in {
	type hint;
	file "named.cache";
};

//---------------end named.conf------------------

Tornado
 

9 More Discussions You Might Find Interesting

1. IP Networking

trying to configure DNS address in Solaris

hi to all. I'm trying to use the sendmail command to generate some reports and I cant use it. The mails i try to send simply won't go out, instead I receive a response from the system sayng that the host is unknown. I think the problem is in the DNS configuration (or the IMAP/SMTP servers). ... (3 Replies)
Discussion started by: ldrojasm
3 Replies

2. UNIX for Advanced & Expert Users

How to configure DNS

My OS is sun solaris7,(sun sparc),i want connect inernet and my computer in my company intranet.After i configure proxy server,i still can't conncet internet.I guess whether the DNS is configured correctly. who can help me???Thank you very much!!! (6 Replies)
Discussion started by: q30
6 Replies

3. UNIX for Dummies Questions & Answers

Add DNS server in Solaris

I am new to UNIX and have been trying to add DNS servers so I can access the internet under Solaris 9. I am using a static IP and have the subnet and gateway configured but cannot figure out to add DNS servers. Does anyone know how to do this? Thank you very much for any help. (1 Reply)
Discussion started by: jmy113437
1 Replies

4. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

5. IP Networking

Configure DNS

I am running Solaris 2.6 Server on a Sparc 10 and I was wondering how I can manually specify a DNS server to resolve hostnames. Any help will be greatly appreciated. And also I have created a file in the /etc dir named defaultrouter and added th IP address of my router, but when I ping another... (15 Replies)
Discussion started by: jskillet
15 Replies

6. Solaris

How to configure Proxy Server in Solaris 10 (X86)

Hi , I have installed solaris 10 on x 86 architecture. Now i want to configure this system as Proxy Server. I am new to the solaris. Please help me how can i configure this. Which packages or patches are needed ? or Which files have to be modify ? Please help me to resolve. Thanks and... (0 Replies)
Discussion started by: raviraj001
0 Replies

7. Solaris

BIND DNS Server issue on Solaris 10

Hi all, I have some sort of problem with BIND DNS server my environment as follows. bash-3.00# cat /etc/release Solaris 10 6/06 s10s_u2wos_09a SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies

8. Solaris

checking Solaris 10 DNS server for IPv6

hi, i have a Solaris 10 DNS server, how do you check whether it can support IPv6 networking ? (0 Replies)
Discussion started by: Exposure
0 Replies

9. Solaris

How to add new Solaris client IP into Solaris 10 DNS server?

Hi, We just built a new Solaris 10 zone. And would like to add it to our DNS server. Its also Solaris 10. Please let me know how can I get the IP resolved using this DNS server. I added entry into zone config file but not working. I did restarted the DNS services. And also added nameserver name... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
named(8)						      System Manager's Manual							  named(8)

Name
       named - Internet name domain server daemon

Syntax
       /usr/etc/named [ -d level# ] [ -p port# ] [ -b bootfile ][ -n ][ -a type.version ]

Description
       The daemon is the Internet domain name server for the BIND/Hesiod service.  Without any arguments, reads the default boot file and any ini-
       tial data from the BIND/Hesiod data base files.	then listens for queries.

       The boot file specifies where the BIND/Hesiod server is to get its initial data.  See the Example section.

       The master data files consist of entries of the following form:
       $include file
       $origin domain
       domain ttl addr-class entry-type resource-record-data
       The entry is useful for separating data into separate files.  The entry is useful for placing more than one domain in a data file.  It  can
       also be used to set the reverse network number origin.  The fields are:

       file	    This is the name of the file to be included.

       domain	    This  is  the  domain  name.  An at sign (@) signifies the current origin.	A name refers to the standard domain name.  If the
		    domain name does not end with a period, the current origin is appended to the domain.  A domain name ending with a	period	is
		    the complete BIND domain name (fully qualified) and thus does not get an extension appended to it.

       ttl	    This  field is an optional integer specifying the time to live.  If no time to live is specified, the default is obtained from
		    the SOA entry.

       addr-class   This field is the object class type.  There are three classes:

		    IN	       Objects connected to the DARPA Internet

		    HS	       Hesiod naming service data

		    ANY        All classes

       entry-type   The most common entries for this field are listed below.  The field, however, must correspond with the entry type:

		    A	       Host address

		    CNAME      Canonical name for an alias

		    HINFO      Host information

		    MX	       Mail exchanger

		    NS	       Authoritative name server

		    PTR        Domain name pointer

		    SOA        Start of a zone of authority

		    TXT        Hesiod text

		    WKS        Well-known service description

       The following signals have the specified effect when sent to the server process using the command:

       SIGXFSZ	    Causes the server to reload only the databases that have changed.

       SIGHUP	    Causes the server to read and reload database.

       SIGINT	    Dumps the current data base and cache to

       SIGIOT	    Dumps statistics to

       SIGUSR1	    Turns on debugging.  Each time the SIGUSR1 signal is issued, the debug level increments  by  one.	Debugging  information	is
		    dumped to

       SIGUSR2	    Turns off debugging.

Options
       -b bootfile  Names of the boot file.  If no boot file is specified, the default is

       -d level#    Prints  debugging  information.   A number after the -d option determines the level of messages printed.  It is a good idea to
		    run the daemon with the -d option in the background.

       -p port#     Specifies the port number.	The default is the standard port number listed in the file.

       -n	    Runs in network safe mode.	All HS class queries sent over the network are authenticated.  Non-authenticated  queries  for	HS
		    information from hosts other than local host are not answered.  Non-authenticated requests for zone transfers are ignored.

       -a type.version
		    Specifies  the  default authentication type.  When authenticated queries are formed, needs to know what type of authentication
		    to use.  The type parameter specifies the form of authentication.  The version parameter specifies the version of the type	to
		    use.  The supported forms of authentication are:

		    type      Kerberos

		    version   One

Examples
       The following is an example of a boot file:
       ;
       ;     boot file for name server
       ;
       ; type	  domain		 source file or host
       ;
       primary	  cities.us		 hosts.db
       ;
       primary	  2.10.in-addr.arpa	 hosts.rev
       ;
       primary	  0.0.127.in-addr.arpa	 named.local
       ;
       secondary  cc.cities.us		 10.2.0.78 128.32.0.10
       ;
       ; load the cache data last
       cache	   .			 named.ca
       Entries	beginning with a semicolon are comment lines.  In this example, the first line that is not a comment specifies that this system is
       the primary authoritative BIND server for the domain This line also specifies that the file contains authoritative  data  for  the  domain.
       Domain names in the file are relative to the origin, such as in the preceding example.

       The second and third non-comment entries (beginning with show the domain in reverse order.  This allows address to name mapping.

       The  fourth  non-comment line specifies that all authoritative data under is to be transferred from the primary master server at IP address
       to the secondary server.  If the transfer fails, the secondary server will then try the master server at address There can be up to  10	IP
       addresses listed.

       The  cache entry specifies that the data in is to be placed in the cache.  This would include well known data such as the locations of root
       domain servers.

Files
       Name server configuration boot file

       Process ID number

       Debug output

       Dump of the BIND server's cache

See Also
       kill(1), signal(3c), resolver(3), hesiod.conf(5), resolv.conf(5)
       Guide to the BIND/Hesiod Service

																	  named(8)
All times are GMT -4. The time now is 08:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy