Name resolving problems

[jayemce]

Hello all,

We use DNS for name resolving.
This is the content of /etc/resolv.conf:

search intranet.domain.com domain.com
nameserver 192.168.0.10
nameserver 192.168.0.11

My problem starts when nameserver 192.168.0.10 is down.
It takes more than 1 minute until the resolving routines switch to the secondary nameserver 192.168.0.11

Can somebody tell if there is a setting or a variable to adapt to force the resolving routines to switch faster to the secondary nameserver?

The /etc/netsvc.conf contains:
hosts=local,bind

Thank you very much in advance
JMC

 

[rzs0502]

What do you have in nsswitch.conf
Try removing file from the hosts section

 

[mrn]

Try adding the line

hosts=local,bind4

to /etc/netsvc.conf





--
| Mike Nixon
| Unix Admin
|
----------------------------

 

[slamcorp]

ancient Chinese secret for this one but it is straight forward in almost ALL unix/linux...

anyhow, what works best for me is;

modifying /usr/include/resolv.h

/*
* Global defines and variables for resolver stub.
*/
#define MAXNS 3 /* max # name servers we'll track */
#define MAXDFLSRCH 3 /* # default domain levels to try */
#define MAXDNSRCH 6 /* max # domains in search path */
#define LOCALDOMAINPARTS 2 /* min levels in name that is "local" */

#define RES_TIMEOUT 1 /* min. seconds between retries */
#define MAXRESOLVSORT 10 /* number of net to sort on */
#define RES_MAXNDOTS 15 /* should reflect bit field size */
#define RES_MAXRETRANS 30 /* only for resolv.conf/RES_OPTIONS */
#define RES_MAXRETRY 3 /* only for resolv.conf/RES_OPTIONS */
#define RES_DFLRETRY 2 /* Default #/tries. */

these are slightly modified, RES-timeout is a major culprit.

I have a long doc I will try to make a faq with it if anyone is interested...works on linux also.

Adam