I’m pleased to announce a yet another release of the New-DJBDNS. The latest version 1.05.8 is now available in source and RPM package format from its home page:

    at ->

Both Fedora and EPEL updates have been pushed and shall be soon available via the stable repositories using Yum(8).

    # yum install ndjbdns

The major and rather important change has been made to the caching server dnscache’s logs. Now these logs are arranged in chronological order with timestamps and readily comprehensible information. Earlier, most of it was cryptic hexadecimal values and numbers.

It is extremely important to have meaningful logs in place along with the secure logging mechanisms. Especially in the light of the recent events like the SEA DNS attack on or little earlier Distributed DoS attack against DNS servers etc. When responding to such events, having meaningful logs in place is but instrumental. Because the logs can tell you about the origins of these requests, quantities and distribution patterns of such requests across multiple sources and continents. A lot many conclusive findings can be derived from carefully crafted logs. But the lack of them could just make the matters equally worse for the defenders.

I planned to include similar updates to the root server tinydns’s logs too, but that got delayed a little because of some travel and work. Other major changes include addition of a new root server to the global list, and a bug fix update to the logrotate(8) configuration file.

I hope you find it helpful. 🙂

3 thoughts on “New-DJBDNS-1.05.8

  1. Hello PJP,

    Thanks for a new version.

    I updated to 1.05.08. But I have to admit I experienced two crashes since then.

    The entries in /var/log/messages:

    Oct 1 01:25:42 nagios kernel: dnscache[14505]: segfault at 12a ip 0000000000409cc9 sp 00007fff1a1fa6b0 error 6 in dnscache[400000+11000]
    Oct 2 01:13:42 nagios kernel: dnscache[27129]: segfault at 12a ip 000000000040b109 sp 00007ffff4a9f450 error 6 in dnscache[400000+13000]

    (Nagios is the name of the machine).

    Any ideas how to further investigate this?
    Add more debugging perhaps?

    Just a coincidence the crashes both appeared few minutes after two o’clock (it logs in UTC and we ‘re 1 hour off here)??


    • Hello Christoph,

      Thank you for your feedback. From the log entries above, it’s difficult to spot when & where(in the source) it crashed. Could you please run it with debug level 3, so that we’ll have detailed log entries to help trace the issue. Also data about DNS requests would be helpful to reproduce the crash.

      It seems you are running Systemd; It’ll help to redirect dnscache(8) logs to a separate file. It can be done by setting Type=forking in the Systemd unit file.

      # cat /usr/lib/systemd/system/dnscache.service

      ExecStart=/usr/sbin/dnscache -d3 -D
      # systemctl daemon-reload –system

      Thank you.

Leave a Reply

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

You are commenting using your 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