Folks,
Recently been looking at servers that host almost 200K ARPA
zones and load about 80 million resource records. They run on good hardware
and take only a few minutes to load the zones on a clean start. The issue is
memory utilization of about 23 Gig in RAM.
Mark Andrews wrote:
>
> That said named does wait for the loading to complete before the
> parent process exits and its exit status reflects if the load
> succeeded or not. See ns_os_daemonize() and ns_os_started().
OK, I'm feeling pretty stupid now, and I'm sorry for saying that named
doesn't d
> On Mar 24, 2016, at 6:28 AM, MURTARI, JOHN wrote:
>
> Folks,
> Recently been looking at servers that host almost 200K ARPA
> zones and load about 80 million resource records. They run on good hardware
> and take only a few minutes to load the zones on a clean start. The i
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 400
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
[mai
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
> spe
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 for
On 24/03/2016 16:18, 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 domain name. Microsoft wants a
> short TTL for their Office 365 records, but I w
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 least, that is what has been
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 domain name. Microsoft wants a short TTL for their
> Office 365 records, but I wou
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 frequently
I tend to agree with you about the overloading of TXT records.
Thanks,
Ben
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Ray Bellis
Sent: Thursday, March 24, 2016 11:22 AM
To: bind-users@lists.isc.org
Subject: Re: Configu
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 ab
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
betwee
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 ret
Thank you for the replies everyone. Are there any major differences between
the BIND package that Red Hat/CentOS provides vs the BIND package provided
by the ISC website?
Thanks
On Thu, Mar 24, 2016 at 8:19 AM, Tony Finch wrote:
> Mark Andrews wrote:
> >
> > That said named does wait for the
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.
> >
> > I'm not that surprised
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:
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 sur
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:
> >>>
> > When I changed our TTLs from 24h to 1h last year, it didn't have a
> > visible
> > effe
19 matches
Mail list logo
