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 ne

Re: Odd A record in our hosts zone file

On 25.06.21 18:29, Bruce Johnson wrote: Thank you…this is very useful information; I thought TTL could only be specified on a per-zone basis, not per-host. not even per-host. Different RR types for the same host can have different TTL. mail1m IN A xxx.xxx.xxx.52;

Re: Odd A record in our hosts zone file

Thank you…this is very useful information; I thought TTL could only be specified on a per-zone basis, not per-host. On Jun 25, 2021, at 11:10 AM, Richard T.A. Neal mailto:rich...@richardneal.com>> wrote: Hi Bruce, Here you're specifying a distinct TTL for those records which overrides the def

Re: Odd A record in our hosts zone file

Time to live in the cache. Short time to live is useful when you need to change the A record to swing one host to another. > On Jun 25, 2021, at 12:56, Bruce Johnson wrote: > > I ran across these A records in one of our zone files: > > ;EXCHANGE STUFF > mail1m IN A

RE: Odd A record in our hosts zone file

Hi Bruce, Here you're specifying a distinct TTL for those records which overrides the default TTL for this zone (which you will have set towards the top of the file with the rest of the defaults) 1m = 60 seconds: https://web.mit.edu/rhel-doc/5/RHEL-5-manual/Deployment_Guide-en-US/s1-bind-zone.h

Odd A record in our hosts zone file

I ran across these A records in one of our zone files: ;EXCHANGE STUFF mail1m IN A xxx.xxx.xxx.52; dhbex1 mail1m IN A xxx.xxx.xxx.54; dhbex2 I can see that this is a cheap load-balancing for our exchange OWA servers, but what is the ‘1m’ no

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 rede

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 (i