Ken,
Please see inserted comments...
Ken Viola wrote:
> Hi All,
>
> Please help us with our DNS issue. We are implementing Netview on AIX (as our
> master Netview) with AMLM's running on NT distributed around the country. The
> AMLM's will offload polling from the AIX Netview and forward status updates
> and
> traps to the master Netview. The Netview is using /etc/hosts currently as we
> are
> in the process of updating DNS to reflect all of our network devices.
I would very strongly recommend getting to an organisation wide DNS under your
NetView. /etc/hosts CANNOT resolve multiple IP addresses to 1 name (for your
routers) - only DNS (or NIS) can do that.
> Netview
> will only be used to manage network devices. It is intended that the Netview
> (AIX) server will act as a secondary caching nameserver only and will not be
> sourced by any other systems.
NetView is a huge user of DNS so I would always put a DNS server on my NetView
system. It improves performance and reliability.
> The issue is whether or not the DNS needs to be
> updated with reverse records for each interface on all of our network devices
> for Netview to function optimally. If the device is able to handle a loopback
> address (ie Cisco routers), our thought is that only the loopback needs to be
> addressed for forward and reverse DNS records.
I would strongly recommend having ALL interfaces in the reverse DNS lookup.
NetView
finds addresses first, not names. The first thing he does having found an IP
address "clue" for his discovery algorithm, is to do a DNS reverse lookup to
try and
find a name for it.
Use loopbacks on your routers where possible. I would then put just the
loopback
into your DNS forward lookup (so when you do "ping box1" or whatever, the DNS
always
resolves to something that is contactable if the box is contactable at all). I
would also use the loopback name in the NetView netmon seedfile if you want to
ensure these devices are found quickly. You still need all the reverse entries
for
your DNS.
> If it is not capable, then one
> interface will have a forward record with every other interface having a
> reverse
> record pointing to it. Is it necessary to provide reverse records for each
> interface if a loopback address can be assigned? We have around 10,000 devices
> and it becomes very tedious and time consuming to require reverse records for
> each interface. What is the best practice to use for the sake of Netview?
> Also,
> if every interface needs to have a reverse record regardless of loopback, are
> there any Perl scripts available to automate the extraction of the interface
> information using snmpwalk with IP(as single parameter or via hosts file) and
> community strings in conjunction with h2n to generate the DNS files?
> Thanks for any help you can provide.
>
> Ken Viola
> kviola@cpcug.org
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
Cheers,
Jane
--
Tivoli Certified Enterprise Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2001 Jane Curry <jane.curry@skills-1st.co.uk>. All rights
reserved.
|