Re: Address match lists syntax, was Managing localhost

No, there is no need to redefine localhost acl. It is built-in and already specifies localhost IPv4 and IPv6 address. similar to localnets (networks directly connected to the server), any or none names. Read a great ARM documentation about BIND [1], it has section about ACLs describing build-in

Re: Managing localhost

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

Re: Address match lists syntax, was Managing localhost

Ooops, sorry. Please forget that. On Fri 25/Jun/2021 12:50:55 +0200 Alessandro Vesely wrote: However, named-checkconf doesn't complain.   I could fix that by defining an acl named localhost.  But do I need to? Now I tried to redefine and got: /etc/bind/named.conf.options:37: attempt to

Address match lists syntax, was Managing localhost

Hi, I found a number of allow-query {localhost;}; and similar stuff in my .conf files. It doesn't seem to be allowed, since the manual says: The elements which constitute an address match list can be any of the following: * an IP address (IPv4 or IPv6) * an IP prefix

Re: Managing localhost

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

Re: Managing localhost

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

Re: Managing localhost

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

Re: Managing localhost

[ 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

Re: Managing localhost

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

Managing localhost

Hi, 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. I do not manage my revers lookup / PTR the IP owner does that. Any thoughts on managing the localhost within the zone