Grant Taylor via bind-users wrote:
> On 6/21/21 11:00 AM, Tony Finch wrote:
> > That advice is out of date: nowadays you should not put any localhost
> > entries in the DNS, because it can cause problems for web browser security.
> > Modern software should suppress queries for localhost so they ne
Am 25.06.21 um 03:22 schrieb Grant Taylor via bind-users:
Tony's statements surprised me enough that I shaved them for later deep
read and pondering. That time has now come.
On 6/21/21 11:00 AM, Tony Finch wrote:
That advice is out of date: nowadays you should not put any localhost
entries
Tony's statements surprised me enough that I shaved them for later deep
read and pondering. That time has now come.
On 6/21/21 11:00 AM, Tony Finch wrote:
That advice is out of date: nowadays you should not put any localhost
entries in the DNS, because it can cause problems for web browser
se
Thank you Kevin and Tony!!
On 2021-06-21 10:07, Kevin Darcy via bind-users wrote:
[ Classification Level: GENERAL BUSINESS ]
That chapter doesn't show any PTR records, for the reverse zones of
any *public* address range, pointing back to a "localhost" name. It
only shows a PTR record in the r
[ Classification Level: GENERAL BUSINESS ]
That chapter doesn't show any PTR records, for the reverse zones of any
*public* address range, pointing back to a "localhost" name. It only shows
a PTR record in the reverse zone for the 127.0.0/24 private range, which is
what enables a reverse lookup f
techli...@phpcoderusa.com wrote:
>
> This book :
> https://www.oreilly.com/library/view/dns-and-bind/0596100574/ch04.html says I
> should manage the localhost within my zone (SOA) and reverse lookup / PTR.
That advice is out of date: nowadays you should not put any localhost
entries in the DNS,
6 matches
Mail list logo
