Hello All,
We have our slave servers running compiled Bind 9.6.1-P3 on CentOS 5.4.
Can I upgrade to 9.8.1-P1 directly from the current version 9.6.1-P3? Or It
has to be on the same 9.6.ESV-R5-P1 latest version?
Master is in internal running on Bind 9.2.1, doing only pusing the
config/zon
I am giving you more details with the hope that maybe someone will give me a
hint.
In named.conf (bind 9.9b2) I have:
# for NXDOMAIN Redirection
zone "." {
type redirect;
file "/etc/bind/zones/redirect.db";
};
redirect.db file contains:
$TTL 300
@ IN SOA ns.example.net host
> I don't understand why Windows doesn't include dig by default, even now.
> Free software hate?
I wonder if it some kind of intellectual property issue. Microsoft has to be
able to sell Windows and therefore must consider any added costs related to
including a component that they do not own a
>
> > I have had a tendency to dig axfr from my Windows workstation
>
> +1 to you for using `dig' on Windows; most don't even know it exists
> and suffer the `nslookup' pain. ;-)
>
First thing I do on a new windows box is download the BIND package and throw
dig on the box ... well, right after
Chris Thompson wrote:
>
> If we are trying to turn Tony's ad hoc command into something publishable,
See the loadzone, axfrzone, and cleanzone functions in
http://www-uxsup.csx.cam.ac.uk/~fanf2/hermes/conf/bind/bin/nsdiff
Writing code to process arbitrary zones is a rather different job from a
q
Jeffry,
> I have had a tendency to dig axfr from my Windows workstation
+1 to you for using `dig' on Windows; most don't even know it exists
and suffer the `nslookup' pain. ;-)
-JP
___
Please visit https://lists.isc.org/mailman/listinfo/bind-us
> dig axfr dotat.at | grep -v RRSIG. Tony.
> dig axfr dotat.at | grep -v RRSIG | grep -v TYPE65534 | grep -v DNSKEY | grep
> -v NSEC3PARAM. JP.
> dig axfr zone | awk '$4 !~ "^NSEC$|^NSEC3$|^RRSIG$" {print}'. Shumon.
Thank you, gentlemen. These are very helpful. As we are primarily Windows
users,
On Nov 24 2011, Shumon Huque wrote:
On Thu, Nov 24, 2011 at 02:29:05PM +0100, Jan-Piet Mens wrote:
On Thu Nov 24 2011 at 13:52:32 CET, Tony Finch wrote:
> I use `dig axfr dotat.at | grep -v RRSIG`
... | grep -v TYPE65534 | grep -v DNSKEY | grep -v NSEC3PARAM
hoping, of course, that n
On Thu, Nov 24, 2011 at 02:29:05PM +0100, Jan-Piet Mens wrote:
> On Thu Nov 24 2011 at 13:52:32 CET, Tony Finch wrote:
>
> > I use `dig axfr dotat.at | grep -v RRSIG`
>
> ... | grep -v TYPE65534 | grep -v DNSKEY | grep -v NSEC3PARAM
>
> hoping, of course, that no owner name is called 'RR
Jan-Piet Mens wrote:
> On Thu Nov 24 2011 at 13:52:32 CET, Tony Finch wrote:
>
> > I use `dig axfr dotat.at | grep -v RRSIG`
>
> ... | grep -v TYPE65534 | grep -v DNSKEY | grep -v NSEC3PARAM
I think it is more useful to see those records than to spend effort
stripping them out.
> hoping,
On Thu Nov 24 2011 at 13:52:32 CET, Tony Finch wrote:
> I use `dig axfr dotat.at | grep -v RRSIG`
... | grep -v TYPE65534 | grep -v DNSKEY | grep -v NSEC3PARAM
hoping, of course, that no owner name is called 'RRSIG' et. al. ;-)
-JP
__
Spain, Dr. Jeffry A. wrote:
>
> From time to time I want to review the current state of the zone files.
> I have been accustomed with v9.8 to taking a copy of a signed zone file
> and stripping out the DNSSEC-related records in a text editor for easy
> review.
I use `dig axfr dotat.at | grep -v R
12 matches
Mail list logo
