[BlueOnyx:18829] Re: BlueOnyx server down

[Chris Gebhardt - VIRTBIZ Internet]

This morning we saw the same thing that Tom reported on a 5209R running 
on Aventurin{e}:

On 12/16/2015 5:56 PM, Tom wrote:
> Hi Michael,
> After seeing this error in the log:
>
> "Dec 16 16:15:07 ns bash: /etc/named.conf:36: open:
> /etc/named.conf.include: file not found"

Changing the reference in the named.conf file to the file's actual 
location fixed the issue, but it broke again as soon as DNS was 
manipulated in the GUI, since the location of named.conf.include was reset.

I created a symlink as follows:
  ln -s /var/named/chroot/etc/named.conf.include /etc/named.conf.include

Then I restarted.

We still get a failure because we see errors like this (for every zone):
Dec 17 14:19:45 web41.virtbiz.net bash[10229]: zone zone.net/IN: loading 
from master file db.zone.net failed: file not found
Dec 17 14:19:45 web41.virtbiz.net bash[10229]: zone zone.net/IN: not 
loaded due to errors.
Dec 17 14:19:45 web41.virtbiz.net bash[10229]: _default/zone.net/IN: 
file not found

Ah, so according to the named.conf file, BIND is looking in /var/named 
for the files, but that's wrong - it should be looking in
/var/named/chroot/var/named/

Interestingly enough, I see this when looking at mounts:
/vz/private/1041 on  (deleted)/var/named/chroot/etc/named.root.key type 
simfs (rw,relatime,usrquota,grpquota)
/vz/private/1041 on  (deleted)/var/named/chroot/etc/named.rfc1912.zones 
type simfs (rw,relatime,usrquota,grpquota)
/vz/private/1041 on  (deleted)/var/named/chroot/etc/named.iscdlv.key 
type simfs (rw,relatime,usrquota,grpquota)


Note the "(deleted)" there.   That doesn't look right.

Not knowing a good way to reset the mount, I restarted the VPS and now 
the simfs for /var/named/chroot entries no longer exists in mtab.   And 
named has the same issue.

So does BIND set up the simfs?

Being in a severely broken state at the moment, I copied the zonefiles 
to /var/named and was able to temporarily start the service, which was 
good enough to get the zones refreshed with our actual nameservers 
again.  That gets things up and running and buys a little time.

However, those caches will expire, so the clock is ticking.

And the temporarily portion of starting named?  Yeah, that's because of 
this:
Dec 17 15:10:25 web41 named[4984]: error (network unreachable) resolving 
'ns4.virtbiz.com/AAAA/IN': 2607:1c00:1:2::2011#53

HUH?  Why are we looking for AAAA records here?   I can't find anything 
that explains that one.
-- 
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ