My named start working -
lame server resolving 'um' (in 'um'?): 137.39.1.3#53
it shutdown shortly after that
I ran across this article on bogus entries from ns.uu.net http://www.ops.ietf.org/lists/namedroppers/namedroppers.199x/msg02558.html
Is that a bad name that is cached above? a restart seems to have fixed it, but I had to be around to fix it and am hoping to prevent that in the future.
I suppose I could create some cron script that parses /var/log/messages for named shutting down and restart it
lame server resolving 'um' (in 'um'?): 137.39.1.3#53
it shutdown shortly after that
I ran across this article on bogus entries from ns.uu.net http://www.ops.ietf.org/lists/namedroppers/namedroppers.199x/msg02558.html
Is that a bad name that is cached above? a restart seems to have fixed it, but I had to be around to fix it and am hoping to prevent that in the future.
I suppose I could create some cron script that parses /var/log/messages for named shutting down and restart it