<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 08:51:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Mark Karpeles' Blog: PHP DNS Daemon]]></title>
      <guid>http://www.phpdeveloper.org/news/11963</guid>
      <link>http://www.phpdeveloper.org/news/11963</link>
      <description><![CDATA[<p>
<i>Mark Karpeles</i> has created something that most people would think he's crazy for - a <a href="http://blog.magicaltux.net/2009/02/16/php-dns-daemon/">DNS daemon written in PHP</a>:
</p>
<blockquote>
If you want to tell me I'm crazy, you can post it in a comment here, it makes me happy. I had some reasons to dislike bind9 which finally made me write my own DNS daemon, and I'll explain that here. My need was to have a stable dynamic DNS server working in most environments, with an easy to configure master/slave relationship (with realtime synchronization), and a way to change records instantly from PHP...
</blockquote>
<p>
Rather than using the (slightly unstable) dlz technology to pull the information from a MySQL database, he opted to roll his own that includes support for:
</p>
<ul>
<li>RFC 1035 standards
<li>realtime data update
<li>slave/master relationship (with a keepalive connection)
</ul>
<p>
Want to try it out for yourself? <a href="mailto:mark@hell.ne.jp">Drop him a line</a> and ask about it!
</p>
<p>
He's also <a href="http://blog.magicaltux.net/2009/02/18/php-dns-daemon-performances/">run some statistics</a> on the performance of the daemon as compared to the standard BIND installation and <a href="http://blog.magicaltux.net/2009/02/19/your-own-php-dns-daemon/">come up with some instructions</a> on how you can install and configure your own instance.
</p>]]></description>
      <pubDate>Tue, 17 Feb 2009 12:06:24 -0600</pubDate>
    </item>
  </channel>
</rss>
