Re: [FreeDNS] Domains not resolving properly

[Rob Hunter <robh@xxxxxxxxxxx>]

Hi

> Also seen:  More than one instance of named which continually and
> mysteriously go belly-up on a signal 11.  And a named which continually and
> mysteriously stops resolving anything.

yes, and this actually happened to me today (9.1.1). I know a few friend
who oddly enough, have their all signal 11 on a sunday, and it was every
sunday for a few weeks in a row.
 
> What with all the BIND holes lately, it's my guess that some script kiddies
> are having a ball.
especially on Sundays :P

> I'ts not currently my job to dig into it, so I steadfastly refuse to spend
> too much time on it.  :-)

hehe. In my case, the mail:

1) wasn't for me
2) was for a domain I'm hosting as a favour

My 'signal 11' this morning was after a valid AXFR attempt from the master
ns of a slave I'm going to be hosting.

Apr 20 09:14:45 hostname named[98]: denied AXFR from [1.2.3.4].1329 for
"xxxxx.com" (not master/slave)

Apr 20 09:30:42 hostname /kernel: pid 98 (named), uid 0: exited on signal
11 (core dumped)


OT: I looked into using djbdns, but when I saw the poor (maybe read:
unfriendly) documentation, and was having a hard time installing it, I sat
and thought to myself what it'd be like if I had a critical problem with
it, and how long it'd take me to fix it. Had to go with bind again (for
now).

later....

--Rob

_____________________________________________________
FreeDNS                    ZA NiC - free domain names
freedns@xxxxxx    Archive: http://www.za.net/freedns/