Thanks for your info.
---------------------
Alain Menezes   
ASLK-CGER Services GIE                          Tel.:  +32 2 228.55.74
Rue Fossé-aux-Loups, 48                               Fax.:  +32 2 228.83.69
1000  Bruxelles                                         Email:
a.menezes AT aslk-cger DOT be




> -----Original Message-----
> From: Robak, Richard [SMTP:richard.robak AT INTEL DOT COM]
> Sent: mercredi 3 mars 1999 15:46
> To:   NV-L AT UCSBVM.UCSB DOT EDU
> Subject:      Re: DNS
> 
> I second James' statements about DNS, and highly recommend using
> DNS caching.  When we started using DNS caching on our AIX systems
> we went from ~4,000 DNS queries an hour to ~100.  In addition, names
> got resolved much quicker.
> 
> My two cents worth,
> 
> Richard Robak
> richard.robak AT intel DOT com
> 
> -----Original Message-----
> From: James_Shanks AT TIVOLI DOT COM [mailto:James_Shanks AT TIVOLI DOT COM]
> Sent: Wednesday, March 03, 1999 6:26 AM
> To: NV-L AT UCSBVM.UCSB DOT EDU
> Subject: Re: DNS
> 
> 
> Alain -
> 
> I seldom save my own appends so I don't have what you are looking for.
> But I can try to tell you a few things about NetView and DNS.
> 
> First, NetView does not know nor care how name resolution is
> accomplished.
> It asks the operating system to do it with calls like gethostbyname
> and
> gethostbyaddress.  And it does this very frequently.  These calls are
> done
> at least twice for every trap by every daemon involved in trap
> processing.
> They are done frequently by netmon and other daemons as well.  So a
> badly
> performing name resolution set up will hurt NetView performance.
> 
> Second, if you are using DNS, then many shops prefer to have their
> name
> servers do nothing else but resolve names so that this happens
> quickly.
> Usually it is not a good idea to put NetView on the box which is the
> primary name server.  Neither one would perform well.  But you can
> make
> NetView a secondary name server.  Note that this is different than a
> backup
> name server, which is where you go when the primary is unavailable.  A
> secondary name server, also called a caching name server, is one which
> gets
> everything it knows about names from the primary.  It loads the
> primary's
> database initially and then requests updates every hour or so (this is
> configurable). The idea here is that this secondary nameserver can be
> local
> or quite close to NetView, so as to minimize network delays.  For
> years,
> AIX performance specialists have recommended that if you have a box
> big
> enough for it, that you put this kind of secondary name server on the
> same
> box as NetView to improve performance.
> 
> Third, I don't do DNS on a regular basis, so someone else will need to
> tell
> you how to set it up.
> 
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
> 
> 
> 
> "MENEZES, ALAIN" <a.menezes AT ASLK-CGER DOT BE> on 03/03/99 07:13:42 AM
> 
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
>       NetView <NV-L AT UCSBVM.ucsb DOT edu>
> 
> To:   NV-L AT UCSBVM.ucsb DOT edu
> cc:    (bcc: James Shanks)
> Subject:  Re: DNS
> 
> 
> 
> 
> 
> I remember James (Shanks) having written an overview about NetView &
> DNS
> some time ago; does anyone have that mail ?
> ---------------------
> Alain Menezes
> ASLK-CGER Services GIE                          Tel.:  +32 2 228.55.74
> Rue Foss