Logging configuration in BIND9


I just want to double-check something. It's regarding logging in BIND9 under Ubuntu Linux. What I have in named.conf.local regarding logging is this:

logging {

    channel debug_log {
         file "/var/log/named/debug.log";
        severity notice;
        print-category yes;
        print-severity yes;
        print-time yes;

    channel query_log {
        file "/var/log/named/query.log";
        severity dynamic;
        print-category yes;
        print-severity yes;
        print-time yes;

    category resolver { debug_log; };
    category security { debug_log; }; 
    category queries { query_log; };

Open in new window

After I turned on my PC, there's something new that was added to debug.log:

02-Nov-2015 19:16:01.684 security: warning: using built-in root key for view _default

And query.log works as usual. Does it mean that both files are getting the info that they should be getting under the conditions set in named.conf.local? Should I just leave it alone for now and IF there're problems with BIND, then I could escalate the severity level to debug 3 for debugging purposes?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What version of BIND are you using?
Logging greatly differs between 9.2 and 9.9 shipped "under Ubuntu Linux"

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David1978Author Commented:

It's ver. 9.9.5 actually. Looks like I managed to figure out how to interpret BIND9's logging (which is definitely more complicated than it should be). Thank you for your desire to help!
To get rid of port conflict and lame server messages you need to type each and every log type in named.conf enabling some and disabling some others.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.