Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

In article , Dave Warren wrote: > On 2016-03-25 07:21, Barry Margolin wrote: > > In article , > > Dave Warren wrote: > > > >> I'm more

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 2016-03-25 07:21, Barry Margolin wrote: In article , Dave Warren wrote: I'm more interested in the impact from the perspective of an authoritative server operator and in some respects sites that use short TTLs

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

> IMHO, memory is so cheap these days that any server that has to eject > cache entries because of memory limits means the server operator isn't > really trying to do their job well. For handling host names, perhaps yes. But it implies sanity on the part of all apps that your clients use. App

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 2016-03-24 18:28, Barry Margolin wrote: In article , Dave Warren wrote: On 2016-03-24 15:20, Tony Finch wrote: Dave Warren wrote: On 2016-03-24 09:46, Ray Bellis wrote: On 24/03/2016 16:41,

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

In article , Dave Warren wrote: > On 2016-03-24 15:20, Tony Finch wrote: > > Dave Warren wrote: > >> On 2016-03-24 09:46, Ray Bellis wrote: > >>> On 24/03/2016 16:41, Tony Finch wrote: > >>> > >

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

Dave Warren wrote: > On 2016-03-24 09:46, Ray Bellis wrote: > > On 24/03/2016 16:41, Tony Finch wrote: > > > > > >When I changed our TTLs from 24h to 1h last year, it didn't have a > > > >visible > > > >effect on authoritative server query load, much to my surprise. > > > >

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 2016-03-24 09:50, Barry Margolin wrote: The problem with this is that when the Office 365 records expire and are removed from the cache, but the other records have not, the server will not know that it should re-query for the O365 records. It still has TXT records in its cache, and it will

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 2016-03-24 09:46, Ray Bellis wrote: On 24/03/2016 16:41, Tony Finch wrote: >When I changed our TTLs from 24h to 1h last year, it didn't have a visible >effect on authoritative server query load, much to my surprise. I'm not that surprised - there's definitely not a linear correlation

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

Some of us tried very hard to have the TXT to SPF migration continue but the working group decided that the transition wasn't happening fast enough and there were "interoperability" issues. Somehow a experiment about which type of data was needed to authenticate email morphed into a experiment

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 24/03/2016 16:41, Tony Finch wrote: > When I changed our TTLs from 24h to 1h last year, it didn't have a visible > effect on authoritative server query load, much to my surprise. I'm not that surprised - there's definitely not a linear correlation between the TTL of an RRset and how

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

In article , Ben Bridges wrote: > TXT records are multiple-purpose. They can be used for SPF records, Office > 365 "MS" records, DMARC records, or whatever arbitrary uses someone dreams > up, all for the same

RE: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

Ben Bridges wrote: > Microsoft wants a short TTL for their Office 365 records, but I would > prefer to generally use a longer TTL for most records (including other > TXT records) in order to reduce the query load on our servers. I gather MS ask for a 1 hour TTL - at

RE: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

TXT records are multiple-purpose. They can be used for SPF records, Office 365 "MS" records, DMARC records, or whatever arbitrary uses someone dreams up, all for the same domain name. Microsoft wants a short TTL for their Office 365 records, but I would prefer to generally use a longer TTL

Re: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

On 24/03/2016 14:47, Ben Bridges wrote: > Greetings. > > > > Is it possible in BIND to configure multiple resource records for the > same domain name, TYPE, and CLASS with different TTL values? For example: > > ... > > I tried it, and BIND set the TTL for all five records to 300 (or more >

RE: Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

This is deliberately forbidden by standard. See RFC 2181, Section 5.2 ("TTLs of RRs in an RRSet") Why would you want to do this? - Kevin From: bind-users-boun...@lists.isc.org

Configuring different TTLs in multiple RRs for the same domain name, TYPE, and CLASS

Greetings. Is it possible in BIND to configure multiple resource records for the same domain name, TYPE, and CLASS with different TTL values? For example: Test-txt.example.com 300IN TXT"Test 300" Test-txt.example.com 400IN TXT"Test