New-DJBDNS: User comments

Hello,

+-- On Thursday, 30 January 2014 6:10 PM, Timbo wrote --+
|First of all, can I say THANK YOU for making DJBDNS useful.
|I've always had to fight with it and seeing it pop up on EPEL
|in a useful rpm format that used service and chkconfig, etc
|really made my day.
|
|I'm basically converting all my servers from using my home-brew
|compiled djbdns to yours.
|...
|Anyway, thanks again for all your great work.
|
|Cheers,
|Tim.

Best email of the week! Thank you Tim!! 🙂

6 thoughts on “New-DJBDNS: User comments

  1. We experienced a crash of dnscache with version 1.05.8 .
    So I decided to update to the current version. Since Friday 1.05.9 crashed twice.
    It’s always just dnscache that crashes, leavin tinydns running.

    I am using MERGEQUERIES=1, but had DEBUG_LEVEL=0.

    I changed the DEBUG_LEVEL to 1 now.
    Anything else I could do to find out what’s making dnscache crash?

    Thank you for your time.

    • Hello Christoph,

      Thank you so much for reporting this issue. To start, you could increase the debug-level to >= 3, to get more details. Second, try running with MERGEQUERIES=0. Third, may I know details about DNS requests around the time when this crash occurs? That’ll be helpful for debugging.

      Thank you.

      • Hello,

        At the time of the crash the following merging actions appeared:

        + merge 192.168.1.126 AAAA proxy.sitepark.local.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA proxy.sitepark.local.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA proxy.sitepark.local.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA ies.sitepark.com.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA ies.sitepark.com.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA ies.sitepark.com.
        + merge 192.175.48.6 PTR 2.100.168.192.in-addr.arpa.
        + merge 192.168.1.126 AAAA ies.sitepark.com.
        + merge 192.175.48.42 PTR 2.100.168.192.in-addr.arpa.

        Debugginglevel was 0 then.

        I’ve changed the level to 3 and MERGEQUERIES to 0.
        I have the feeling this way the crashes won’t reappear.

        I have enabled a watchdog, a little perl script which start the dnscache if it stops working.

        So I could help in trying to make the crashes appear again and perhaps find the problem.

        Greetings and Thanks

  2. We’ve had a few crashes in the last days with MERGEQUERIES= 0 and DEBUGGING set to 3 (I think).
    I can provide some logfile excerpts. Perhaps via E-Mail?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s