Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77360
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.43 as permitted sender)
MIME-Version: 1.0
Date: Fri, 19 Sep 2014 19:15:32 -0700
Message-ID: <CAKOpQSyiCDEUDGhn50RuLL7ox_TJCCjD=4=qZ68OqbA5krXWkA@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013a110ed69f7b050375ca16
Subject: [RFC] Change checkdnsrr() $type argument behavior
From: kris.craig@gmail.com (Kris Craig)

--089e013a110ed69f7b050375ca16
Content-Type: text/plain; charset=UTF-8

Per discussion in an earlier thread.  Here's the RFC:

https://wiki.php.net/rfc/checkdnsrr-default-type


Basically, this RFC seeks to make it so that PHP's checkdnsrr() function,
which is most commonly used to see whether or not a hostname exists, no
longer restricts itself to only MX records by default.

Though the RFC itself is a no-brainer, the more difficult question is which
solution should be implemented.  The two options currently presented are
changing default from "MX" to "ANY", which would cause it to check all
records and not just MX; and getting rid of the default altogether and
making it so that the argument is required.

From what I can tell, there are valid arguments to be made for both, so I
would love to see some discussion/debate here regarding which solution
should be implemented, as I'm currently undecided.  Also please feel free
to point out any areas of improvement for the RFC itself.

--Kris

--089e013a110ed69f7b050375ca16--