My final decision was to move DNS service off the machine that serves NIS, since the NIS clients have to have an entry for their server in /etc/hosts, this was throwing me off to no end..
Plus, yes, I've been rewriting my config files, but not because they're inappropriately built, but because they have somewhat wrong data, and I hadn't noticed before. > -----Original Message----- > From: Terry Boon [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 30, 2001 2:24 PM > To: debian-user@lists.debian.org > Subject: Re: BIND not working (was RE: NFS hangups.) > > On Tue, Jan 30, 2001 at 09:20:49PM +0000, Terry Boon wrote: > > > On Tue, Jan 30, 2001 at 12:21:46PM -0800, Alex Swavely wrote: > > > I think I figured it out... BIND was just upgraded on this > > > machine, the security release, and the only clients that have been > > > able to connect all had this server listed in their /etc/hosts > > > files. > > > > > > So the issue now is BIND not working correctly. > > > > You may want to check the recent thread (started yesterday) with the > > subject "Broken reverse DNS - after recent bind upgrade?" > > > > That was my call for help when the bind upgrade stopped my DNS working > > properly. The consensus appears to be that I need to reformat my > > configuration files. (I've still to test that it works.) > > (Apologies for following up to myself...) > > I've just reread (ie read properly) the responses to my original > message. I wrote above "...I need to reformat my configuration > files"; this should probably say "...I need to rewrite my > configuration files so they are correct". > > In short, I'd got the syntax of the SOA line incorrect; the old bind > was happy with it (although how it understood it, I don't know), but > the new bind interpreted it "properly" and rejected it. > > Terry Boon >
