Thank you for all the good responses.
While I am unsure if Chrisoph's question was answered, I now understand
why most everyone thinks it is a bad idea to over-ride the TTL for
records I am not authoritive for:
1) It's not RFC compliant for the protocol
2) Changing it could potentially increase
After noodling it out with a co-administrator, that is the same
conclusion we came to.
Thank you for confirming it.
Brian
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
I'm looking for methods to reduce the period of time we cache external
records (e.g., www.google.com). I think the option I need to implement
is max-cache-ttl.
Is this the correct method for limiting caching? Are there reasons that
I should or should not do it?
Thanks,
Brian
Sent: Thursday, September 23, 2010 10:37 AM
To: bind-users@lists.isc.org
Subject: Re: Max-Cache-TTL
On 9/23/2010 10:19 AM, Atkins, Brian (GD/VA-NSOC) wrote:
I'm looking for methods to reduce the period of time we cache external
records (e.g., www.google.com). I think the option I need to implement
I'm running 9.6 in our lab environment with DNSSEC enabled, not much
difficulty at all. To make it even easier, you might want to look at the
Webmin BIND module. It makes it even easier.
shameless plugAlso, I went to ISC's BIND deployment workshop and found
it very insightful. /shameless plug
Kevin,
Thanks for the good ideas. Here is what I am seeing based on your
recommendations:
1. Zone has expired (to confirm: check logs)
No errors or notices regarding the zone being expired.
2. Corrupted/truncated journal file (to confirm: check logs, or, shut
down gracefully, delete journal and
Thanks to everyone who replied to my questions yesterday. I gleaned some
very useful information from the conversations.
Using some of the suggestions, I kludged together another script. I'm
still fine tuning it. It works great for A and CNAME records, but I'm
tweaking the MX and NS record types.
Does anyone know of an existing script or program that can parse a zone
file and verify records against an active server?
I'm attempting to clean up some large zone files and want to ensure that
none of the changes will break DNS when I implement it. Later, I'd like
to use it to verify that the
with actual verification of the records.
Brian
-Original Message-
From: wllarso [mailto:wlla...@swcp.com]
Sent: Thursday, July 22, 2010 12:45 PM
To: Atkins, Brian (GD/VA-NSOC)
Cc: bind-users@lists.isc.org
Subject: Re: Script for verifying zone files
On Thu, 22 Jul 2010 11:44:55 -0400
After specifying MX records for a 2nd tier domain, is it necessary to
restate the MX records for a new $ORIGIN? For example, if I have:
$ORIGIN .
...
IN MX 10 mx1.example.com.
IN MX 10 mx2.example.com.
IN MX 10
the ability to GSLB.
Is that a correct statement?
Brian
-Original Message-
From: bind-users-bounces+brian.atkins2=va@lists.isc.org
[mailto:bind-users-bounces+brian.atkins2=va@lists.isc.org] On Behalf
Of Atkins, Brian (GD/VA-NSOC)
Sent: Wednesday, July 21, 2010 1:15 PM
To: bind
11 matches
Mail list logo
