In message <6eb799ab1002141824s652c4f31od02cb750912a0...@mail.gmail.com>, James
Hess writes:
>
> Also, BIND implements the EXPIRE value in the SOA.
> But other DNS server software applications widely ignore this value,
> and the zone stays authoritative on all servers, no matter how much
>
On 2/14/2010 8:14 PM, Jon Lewis wrote:
>> The glue and all of that stuff won't expire at TTL=0?
>
> No. Authoratative data on your server (a locally configured zone) doesn't
> require glue.
I really should have scrapped that reply and started over--by the time I
got to this part I realized tha
On Sun, Feb 14, 2010 at 7:55 PM, Larry Sheldon wrote:
> I understand that--but it the TTL is being managed correctly the server
> answering authoritatively ought to stop doing so when the TTL runs out,
> since it will not have had its authority renewed.
The TTL can never "run out" on an author
On Sun, 14 Feb 2010, Larry Sheldon wrote:
I understand that--but it the TTL is being managed correctly the server
answering authoritatively ought to stop doing so when the TTL runs out,
since it will not have had its authority renewed.
That's not how things work. If you configure bind to be a
On 2/14/2010 7:48 PM, Scott Howard wrote:
> On Sun, Feb 14, 2010 at 5:19 PM, Larry Sheldon wrote:
>>> It is possibly to run both Authoritative and Recursive server on the
>>> same IP, but it's generally not recommended for many reasons (the most
>>> simple being that of stale data if your server i
On Sun, Feb 14, 2010 at 5:19 PM, Larry Sheldon wrote:
>> It is possibly to run both Authoritative and Recursive server on the
>> same IP, but it's generally not recommended for many reasons (the most
>> simple being that of stale data if your server is no longer the
>> correct nameserver for a dom
On 2/14/2010 6:21 PM, Scott Howard wrote:
> A "resolver" is basically a client.
>
> There's two types of resolvers - recursive resolvers (that look after
> doing the full resolution themselves - starting at the root servers
> and working down), and "stub resolvers" which are only smart enough
> pa
On 2/14/2010 6:10 PM, Rob Austein wrote:
> At Sun, 14 Feb 2010 18:02:48 -0600, Laurence F Sheldon, Jr wrote:
>>
>> I thought I understood but from recent contexts here it is clear that I
>> do not.
>>
>> I thought a resolver was code in your local machine that provide
>> hostname (FQDN?), given ad
A "resolver" is basically a client.
There's two types of resolvers - recursive resolvers (that look after
doing the full resolution themselves - starting at the root servers
and working down), and "stub resolvers" which are only smart enough
pass the entire request onto another server to handle.
At Sun, 14 Feb 2010 18:02:48 -0600, Laurence F Sheldon, Jr wrote:
>
> I thought I understood but from recent contexts here it is clear that I
> do not.
>
> I thought a resolver was code in your local machine that provide
> hostname (FQDN?), given address; or address, given host name (with
> assi
10 matches
Mail list logo
