On Sat, Apr 06, 2002 at 03:48:05AM +0200, Brian Ipsen wrote: > > Doing a lot of debugging on the code finally indicated the problem: Even > though I specified: > > monitor dns.monitor -zone example.com -master ns1.example.com > ns1.example.com ns2.example.com > > the dns.monitor still made queries towards localhost ??? Somehow localhost > is added to the list/array of nameservers to check, so I had to patch it out > in the dns.monitor file.... Probably not the right way to do it, because it > makes it impossible to specify localhost as DNS server (you could use > 127.0.0.1 instead)... Don't know if it's a bug in dns.monitor of a bug in > mon .....
My mon.m4 has this: monitor dns.monitor -zone hotwired.com -master ns1.hotwired.com Are you trying to specify the hosts as parameters to dns.monitor? From the man page (http://www.kernel.org/software/mon/man/mon.html): MONITOR PROGRAMS Monitor processes are invoked with the arguments specified in the configuration file, appended by the hosts from the applicable host group. For example, if the watch group is "servers", which contain the hostnames "smtp", "nntp", and "ns", and the monitor line reads as follows, monitor fping.monitor -t 4000 -r 2 then the exectuable "fping.monitor" will be executed with these parameters: MONITOR_DIR/fping.monitor -t 4000 -r 2 smtp nntp ns So you don't need to give all those hosts. Are you trying to specify multiple masters or something? OBTW, please reply to the list, just because I responded once doesn't mean I want to take this on single-handedly. -- Nate "A UNIX saleslady, Lenore Likes work, but likes the beach more. She found a clever way To mix work with play... She sells C shells by the seashore."
