|
Softpanorama |
May the source be with you, but remember the KISS principle ;-)
|
janl@math.uio.no
HOWTO become a totally small time DNS admin.3. A caching only name server.
- 5.1 /etc/named.conf (or /var/named/named.conf)
- 5.2 /var/named/root.hints
- 5.3 /var/named/zone/127.0.0
- 5.4 /var/named/zone/land-5.com
- 5.5 /var/named/zone/206.6.177
DNS can be intimidating at first. What files do I modify? What do I put in them? How does it apply to Solaris, specifically? If you're used to another operating system, Solaris, like any new platform - might not be immediately obvious, as there are a few pecularities you should be aware of. This article will discuss DNS related issues under Solaris, using version 7 as the reference platform and the stock Sun version of BIND.
Further down, BIND v9.1.0 will be discussed as an upgrade to the stock version. You should definately consider upgrading this way, as there are several security holes that can compromise root on your box with the stock BIND v8.1.2 that ships with Solaris 7.
A few key terms to understand are needed before we dive in. BIND refers to the software that you will be interacting with. What it does is provide a domain name server (DNS) that translates hostnames into valid (hopefully) IP addresses. When it is running on your system, you will often see a process called named or in.named.
It's really quite simple to get going and keep DNS maintained. We won't be getting too involved in complex DNS setups, but will illustrate all the basics needed to get most jobs done and get you up and running in the least amount of time.
There are several ways to provide a name resolution to your local machine and it's users or to your entire office - or even the Internet in general. Among the possibilities are:
- Local resolution of local machines outside of BIND
- Internal use only name server
- Completely external name resolution
- External name resolution with local caching
- Being the authoritative DNS server for your domain(s)
Depending on these needs determines how you will be setting up DNS and which files are to be modified and maintained. You should decide ahead of time what your needs are, but keep in mind that you can always modify this behavior at a later time quite readily.
Goals for this Article
Outdated:
http://cramsession.brainbuzz.com/cramsession/microsoft/win2knet_infra/guide.asp
Spitzner, Lance. "DNS Access."
26 January 2000.
URL: http://www.enteract.com/~lspitz/rules/rule6.html
(21 July, 2000).
Gray, Damon. "The "IN-ADDR.ARPA"
domain and it’s relation to DNS."
URL:
http://www.wednet.edu/network/whitepapers/in-addr.arpa.domain-whitepaper.html
(23 July, 2000).
Files needed on primary nameserver (Change db.mydomain.com to db.[whatever your domain is] and db.192.168.222 to db.[whatever your class C is]):
Files needed on secondary nameserver
Note that the locations and names of these files can vary quite a bit, but this naming scheme will work fine.
Index of pubdocsunix-tutorials courses
Copyright © 1996-2008 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. Submit comments This document is an industrial compilation designed and created exclusively for educational use and is placed under the copyright of the Open Content License(OPL). Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
Standard disclaimer: The statements, views and opinions presented on this web page are those of the author and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Created May 16, 1996; Last modified: February 28, 2008