I'm not sure how long it will continue, but the archives can currently be found
at http://www.vk.net/tivoli/Netview-List.nsf/main?openview
As for DNS, you can get the latest version of BIND (9.2.1) from here
http://www.isc.org/products/BIND/bind9.html
Keep reading the DNS & BIND 4th edition, there are lots of examples in there.
Here is the config from a 9.2.1 server I'm just setting up:
key "rndc-key" {
algorithm hmac-md5;
secret "OfE09nFeAww8tGPIpJnhkA==";
};
key "ddns-key." {
algorithm "hmac-md5";
secret "czGFjMbiwPGWHw8FXqxxqA==";
};
key "craig-key." {
algorithm "hmac-md5";
secret "n5hRBqyKBPe2bDo2dSFeWA==";
};
server 162.131.154.83 {
keys { ddns-key. ; };
};
server 162.131.161.133 {
keys { craig-key. ; };
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
options {
directory "/usr/local/named"; // Working directory
pid-file "named.pid"; // Put pid file in working dir
allow-query { any; };
forward only;
forwarders { 162.131.2.17; 162.131.5.112; 162.131.87.8; 162.131.46.68; }
;
};
logging {
channel my_syslog {
syslog daemon;
// Debug messages will not be sent to syslog, so
// there is no point to setting the severity to
// debug or dynamic; use the lowest syslog level: info.
//
severity info;
};
channel default_log_file {
file "/usr/local/named/logs/named.log" versions 5 size 1M;
print-time yes;
print-category yes;
print-severity yes;
};
category default { default_log_file; my_syslog; };
};
// Root server hints
zone "." { type hint; file "root.hint"; };
//================================================================
//
// Forward domain definitions
//
zone "principal.com" IN {
type master;
file "db.principal.com";
allow-update {none; };
allow-transfer { any; };
};
//
//================================================================
//================================================================
//
// Reverse domain definitions
//
//
// Provide a reverse mapping for the loopback address 127.0.0.1
//
zone "0.0.127.in-addr.arpa" {
type master;
file "db.0.0.127";
notify no;
};
//
//
zone "131.162.in-addr.arpa" IN {
type master;
file "db.131.162";
allow-update { key ddns-key.; key craig-key.; };
allow-transfer { any; };
};
//
//================================================================
I'm not sure about the best h2n, but it can't be that hard to whip that out
yourself.
In production, I actually just run a caching-only DNS server on the Netview
machine, but you're method should work, too. I chose the caching-only route,
because it was easier for me to maintain the networking devices in the regular
DNS master and just use the caching server to speed DNS lookups on the Netview
server.
-----Original Message-----
From: Scherting, Mark [mailto:mscherting@state.mt.us]
Sent: Tuesday, July 09, 2002 3:34 PM
To: 'nv-l@lists.tivoli.com'
Subject: [nv-l] Implementing DNS for NV on AIX
Hi all,
I've been off the list for a bit and am now jumping back into the fray with
a couple of questions. First, where are the list archives now?
Second, I've been asked to look into implementing DNS on my NV/AIX 4.3.3 box
to manage a zone containing just our network devices and from which our
primary DNS would load this zone. Has anyone done something like this?
Please point me toward some AIX specific examples, Redbooks, etc. I've read
the O'Reilly DNS & Bind book for the concepts but would like to see some
configuration examples in black & white.
Any recommendations on which version of Bind and h2n to use and where to get
them? Are there any newer/better tools than h2n for AIX?
Thanks!
Mark Scherting
State of Montana
Information Technology Services Division
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|