>
> I had problems with the new 'AUTH' statements; even when my servers were
> authoritative they would come up. I removed the AUTH statement and it
> works OK (of course you lose the functionality that the AUTH statement
> gives you)
>
I think you've got it implemented wrong.
What this says is "I have a domain, istar.ca . The first server
thats authoritative for is is called mail, its at 154.11.136.66. The
second server is called news, its at 154.11.136.66. The third.............."
I believe it only has the ability to tell you that the server is
authoritative for the domain, not hosts in the domain.
We have a domain, ariesorchids.com . According to the NIC:
------------------------------------------------------------------------------
Domain servers in listed order:
MIDGAARD.TTSG.COM 165.254.99.107
VALHALLA.STORMKING.COM 204.141.98.1
FRIGG.TTSG.COM 209.51.161.86
------------------------------------------------------------------------------
So, I put the following in my files :
==============================================================================
DOMAINNAME ariesorchids.com
arieso-midgaard 165.254.99.107 AUTH
arieso-valhalla 204.141.98.1 AUTH
arieso-frigg 209.51.161.86 AUTH
==============================================================================
Tuc/TTSG
> On Thu, 27 Aug 1998 jhenders@bogon.com
> wrote:
>
> >
> > I noticed a couple of problems with nsmon today when routing to one of
> > our nameservers went down. I have a config file that looks like this.
> >
> > DOMAINNAME istar.ca
> > #
> > mail 154.11.136.66 AUTH
> > news 154.11.136.66 AUTH
> > home 154.11.136.66 AUTH
> > auth 154.11.136.66 AUTH
> >
> > and the netconsole and log output ends up looking like this.
> >
> > Site Address Time +-Variable-+ +-Value-+ Condition
> >
> > istar.ca 154.11.136.66 15:40 named-status 0 Warning
> > istar.ca 154.11.136.66 15:40 named-status 0 Warning
> > istar.ca 154.11.136.66 15:40 named-status 0 Warning
> > istar.ca 154.11.136.66 15:40 named-status 0 Warning
> > istar.ca 154.11.136.66 15:40 named-status 0 Warning
> >
> > Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
> > Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
> > Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
> > Thu Aug 27 13:23:00 1998 [nsmon]: SITE istar.ca 154.11.136.66 VAR named-status 0 0 SOA LEVEL Critical LOGLEVEL Critical NOCOP down
> >
> > Wouldn't it be more useful if the site was listed as mail.istar.ca,
> > news.istar.ca, etc?
> >
> > Also when the site was reachable I don't seem to have got up messages in
> > the data or log files so the sites stayed flagged in netconsole until I
> > restarted nsmon.
> >
> > --
> > Artificial Intelligence stands no chance against Natural Stupidity.
> > GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
> > b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
> >
>
> Thank you,
>
> Jonathan A. Zdziarski
> Senior Systems Administrator
> Netrail, Inc.
> 888.NET.RAIL x242
>
|