Show
Ignore:
Timestamp:
01/16/04 23:18:12 (9 years ago)
Author:
ahu
Message:

lots

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • trunk/pdns/pdns/docs/pdns.sgml

    r210 r215  
    1212    </author> 
    1313     
    14     <PubDate>v2.1 $Date: 2003/12/17 19:55:44 $</PubDate> 
     14    <PubDate>v2.1 $Date: 2004/01/16 22:18:12 $</PubDate> 
    1515     
    1616    <Abstract> 
    … …  
    8383      </para> 
    8484 
    85     <sect2 id="changelog-2-9-13"><title>Version 2.9.13</title> 
     85    <sect2 id="changelog-2-9-14"><title>Version 2.9.14</title> 
     86        <para> 
     87          Big release with the fix for the all important 2^30 seconds problem and a lot of other news. 
     88        </para> 
     89        <para> 
     90          <itemizedlist> 
     91            <listitem> 
     92              <para> 
     93                errno problems would cause compilation problems when using LDAP (Norbert Sendetzky) 
     94              </para> 
     95            </listitem> 
     96            <listitem> 
     97              <para> 
     98                The Generic SQL backend could cause crashes on PostgreSQL when using pdns_control notify (Georg Bauer) 
     99              </para> 
     100            <listitem> 
     101              <para> 
     102                If using the master or slave features, pdns had the notion of eternity ending in 2038, except that due 
     103                to a thinko, eternity ended out to be the 10th of January 2004. This caused a loop to timeout immediately. 
     104                Many thanks to Jasper Spaans for spotting the bug within five minutes. 
     105              </para> 
     106            </listitem> 
     107            <listitem> 
     108              <para> 
     109                Parts of the SOA field were not connonicalized 
     110              </para> 
     111            </listitem> 
     112            <listitem> 
     113              <para> 
     114                The loglevel could in fact cause nothing to be logged (Norbert Sendetzky) 
     115              </para> 
     116            </listitem> 
     117          </itemizedlist> 
     118        </para> 
     119        <para> 
     120          Improvements: 
     121          <itemizedlist> 
     122            <listitem> 
     123              <para> 
     124                The recursor now chooses the fastest nameserver, which causes a big speedup! 
     125              </para> 
     126            </listitem> 
     127            <listitem> 
     128              <para> 
     129                LDAP now has different lookup models 
     130              </para> 
     131            </listitem> 
     132            <listitem> 
     133              <para> 
     134                Cleanups, better load distribution, better exception handling, zone2ldap improvements 
     135              </para> 
     136            </listitem> 
     137            <listitem> 
     138              <para> 
     139                The recursor was somewhat chatty about TCP connections 
     140              </para> 
     141            </listitem> 
     142            <listitem> 
     143              <para> 
     144                PostgreSQL now only depends on the C API and not on the deprecated C++ one 
     145              </para> 
     146            </listitem> 
     147            <listitem> 
     148              <para> 
     149                PowerDNS can now fully overrule external zones when doing recursion. See <xref linkend="recursion">. 
     150              </para> 
     151            </listitem> 
     152          </itemizedlist> 
     153        </para> 
     154      </sect2> 
     155      <sect2 id="changelog-2-9-13"><title>Version 2.9.13</title> 
    86156        <para> 
    87157          Big news! Windows is back! Our great friend Michel Stol found the time to update the PowerDNS code so it works  
    … …  
    43594429        </para> 
    43604430        <para> 
    4361           When chrooting PDNS, take care that backends will be able to get to their files. Many databases need access to a UNIX  
    4362           domain socket which should live within the chroot. It is often possible to hardlink such a socket into the chroot dir. 
     4431          <warning> 
     4432            <para> 
     4433              When chrooting PDNS, take care that backends will be able to get to their files. Many databases need access to a UNIX  
     4434              domain socket which should live within the chroot. It is often possible to hardlink such a socket into the chroot dir. 
     4435            </para> 
     4436            <para> 
     4437              When running with master or slave support, be aware that many operating systems need access to specific libraries 
     4438              (ofen <filename>/lib/libnss*</filename>) in order to support resolution of domain names! You can also hardlink these. 
     4439            </para> 
     4440          </warning> 
    43634441        </para><para> 
    43644442          The default PDNS configuration is best chrooted to <filename>./</filename>, which boils down to the configured location 
    … …  
    46994777      <para> 
    47004778        To make sure that the local authoritative database overrides recursive information, PowerDNS first tries to answer a question from its own database. 
    4701         If that succeeds, the answer packet is sent back immediately without involving the recursor in any way. 
     4779        If that succeeds, the answer packet is sent back immediately without involving the recursor in any way. This means that for questions for which there is no answer, PowerDNS will consult the recursor for an recursive query, even if PowerDNS is authoritative for a domain! This will only cause problems if you 'fake' domains which don't really exist. 
     4780      </para> 
     4781      <para> 
     4782        If you want to create such fake domains or override existing domains, please set the <command>allow-recursion-override</command> feature (available as of 2.9.14). 
    47024783      </para> 
    47034784      <para>