Bind errors??

[Ray]

On Mon, 5 Jun 2000, Barry Margolin wrote:

> In article <Pine.LNX.4.10.10006051304041.24453-100000 at romulus.csd.selu.edu>,
> Ray  <ray at ops.selu.edu> wrote:
> >
> >Hello all,
> >
> >I'm migrating our DNS from 2 VMS machines to 2 Linux machines.  I thought
> >everything looked good, clients and servers have been using the new DNS
> >servers for a week now.   But this weekend, when VMS was brought down for
> >an upgrade, my primary Linux DNS server stopped responding.
> >
> >I'm not positive they are related, but strongly suspect so.  This is
> >relevant entries from the log while DNS was down...  i'm particularly
> >concerned with the "Broken pipe" and "Connection refused" messages.   When
> >VMS came back up, named apparently fixed itself.....    Anyone have any
> >ideas about the logs?  I'd appreciate it...
> 
> It would help if you told us whether the addresses that show up in the log
> (e.g. 147.174.1.5, 147.174.247.80, etc.) correspond to the VMS servers.

147.174.1.4 and 147.174.1.5 are the primary and secondary linux
nameservers, respectively.  The log i'm posting came from the primary
linux server.  147.174.1.7 and 147.174.1.8 are the VMS servers.  The VMS
name servers don't seem to show up in the logs... 147.174.247. is a dhcp
subnet...so not worried about that.

> My first guess is that you may have had the Linux machines configured to
> forward to the VMS machines.

No...this is the options on primary linux, no fowarding:

options {
        directory "/var/named";
        listen-on { 147.174.1.4; 127.0.0.1; };
        allow-transfer { 147.174.1.4; 147.174.1.5; 147.174.1.6;
147.174.1.7; 147.174.1.8; 192.239.16.129; };
        query-source address 147.174.1.4 port * ;
};


> Without more details about the configuration of the Linux boxes, it's
> difficult to say much more.

Sorry... i fired off that message a little hastily. :)  The only thing i
can think of is namserver records at Internic for our domain SELU.EDU are
still pointing to the VMS servers.  I knew this would affect external
sites trying to connect to us, but i didn't think it would affect internal
clients connectivity... could this be an issue??  thanks again for any
insight...

later!
Ray