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
bindsetup(8)						      System Manager's Manual						      bindsetup(8)

Name
       bindsetup - set up the Berkeley Internet Name Domain (BIND)/Hesiod service

Syntax
       /usr/etc/bindsetup [ -c [ -d directory ] -b binddomain  name1,IP1 name2,IP2 ...	]

Description
       The command sets up the Berkeley Internet Name Domain (BIND)/Hesiod service on your system and places and resolution under BIND/Hesiod con-
       trol.  You can use this command to set up your system as a primary, secondary, slave, or caching server, or as a client.

       In order to run BIND/Hesiod, your system's host name must include the BIND domain name.	The BIND host name consists of the local host name
       plus  the  BIND	domain	name,  separated by periods.  For example, the BIND host name for a system whose local host name is and whose BIND
       domain name is is

       The command edits the and files and changes the local host name to the BIND host name, if it is not there already.

       If the command changes your system's host name, you should reboot the system to be sure that the change is propagated throughout  the  sys-
       tem.

       Before  you  run , your system must be established on a local area network.  In addition, you must know the BIND domain name for your local
       area network, and whether your system will be a primary, secondary, slave, or caching server, or a client.

       The command asks if you want to run a Kerberos authentication server. You must already have set up Kerberos to do do.   For  more  informa-
       tion, see the Guide to Kerberos.

       You should run the command as superuser and with the system in multiuser mode.

       If you use the option with the respective arguments, the command sets up your system as a BIND/Hesiod client non-interactively.

       If you run the command with no arguments, a menu is displayed giving you a choice of responses.	You are then prompted for further informa-
       tion.  Before exits, it lists the files that have been updated.

       Once BIND/Hesiod is installed on a machine, it cannot be used until the file is modified to contain BIND entries on  the  desired  database
       lines.  The command reminds a user to run or edit the file manually.

Options
       -c	    Sets up your system as a BIND/Hesiod client according to the following arguments you supply on the command line:

       -d   directory
		    This  option and argument are required if you are setting up a diskless client from the diskless server.  The directory is the
		    full path name of the root directory for your system (a diskless client) on the diskless server.  The following is an  example
		    of a root directory for a diskless client named
		    /dlclient0/orange.root

       -b   binddomain
		    This is the name of the BIND domain on which your system will be a BIND client.  For example, is a sample BIND domain name.

       name,IP	    This is the host name and the IP address of the BIND server on the domain, for example You can specify one or more BIND server
		    by listing more name,IP arguments, each separated by a space.

Files
       List of locally maintained host names and IP addresses

       Startup commands pertinent to a specific system

       Database name with the selected naming services

       Hesiod configuration file

       List of Kerberos servers

       Default BIND Files:

       BIND server data file directory

       BIND server boot file

       BIND server cache file

       BIND server local host reverse address host file

       BIND primary server hosts file

       BIND primary server reverse address hosts file

       BIND data file

See Also
       nslookup(1), hesiod(3), hesiod.conf(5), svc.conf(5), svcsetup(8), named(8), krb.conf(5), resolv.conf(5)
       Guide to the BIND/Hesiod Service
       Guide to Kerberos

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