On 2012-06-08 at 15:36 +1000, Mark Andrews wrote:
> Apply the following. It should work
>
> diff --git a/bin/named/controlconf.c b/bin/named/controlconf.c
[...]
Confirmed, works for me, thank you!
-Phil
___
Please visit https://lists.isc.org/mailman/l
> What have I done wrong or not done correctly following the installation?
This is discussed in the release notes for BIND 9.9.
The default masterfile format for slave zones is now "raw" instead of
"text". When you upgrade your server, it will try to load the zones using
raw format. Since they
please share configuration and possibly zone file(s) so we can help...
if your isp has done rfc2317 style delegation, your servers are actually
authoritative so i don't think it has anything to do with allow-recursion
(and i doubt you want to set that to any, unless you have network acls in
place
Hi--
On Jun 8, 2012, at 1:08 PM, Mike Bobkiewicz wrote:
> we are running an authorative name server for some domains. After some time
> our ISP has now delegated the reverse name lookups to our server. We are
> running bind 9.7.3 on Mac OS X 10.6 and are not able to bring the reverse
> name loo
Dear list,
we are running an authorative name server for some domains. After some time our
ISP has now delegated the reverse name lookups to our server. We are running
bind 9.7.3 on Mac OS X 10.6 and are not able to bring the reverse name lookups
to life. The master db-file is loaded and we to
> Probably nothing. I believe the default format for slave zones is now
> compiled rather than text. Remove all the zone files on the slave and
> reload it.
... after defining `masterfile-format text;' :-)
-JP
___
Please visit https://lists.isc
Probably nothing. I believe the default format for slave zones is now compiled
rather than text. Remove all the zone files on the slave and reload it.
Chris Buxton
BlueCat Networks
On Jun 8, 2012, at 12:26 PM, David L. Beem wrote:
> Just upgraded to 9.9.1 from 9.8.0, the end results seem to be
Just upgraded to 9.9.1 from 9.8.0, the end results seem to be reported
correctly from both master and slave. Master (running on 2003 R2) is
unaffected. Slave (2008 SP2) puts corrupted (text with additional special
characters) zone files in the directory when the service is restarted, and
creates ad
If it were me I'd just block access with iptables (and maybe blackhole as well
if I were sufficiently concerned) and combine that with the iptables log action…
W
On Jun 8, 2012, at 1:44 PM, wrote:
> All,
>
> We have a list of DNS servers that we do not want our BIND DNS server
> interacting
All,
We have a list of DNS servers that we do not want our BIND DNS server
interacting with. We can put the IP addresses of those servers in the
blackhole substatement under options. Is there a way to monitor for when our
DNS server tries to communicate with servers that are in the blackhole li
Will bind run on VMware?
Yes, if the guest operating system supports it.
Of more interest to me is: are there limitations?
Types of configs or workloads that should
not be run under VMware?
John
P.S. Aps are sometimes distributed bundled with an OS,
i.e., forming a package that does run dir
Some updates:
Eventually got VirtualBox to behave and now have two virtual instances
of Gentoo/BIND on my box. Now I have a cleaner test environment.
Rebuilt Evans demo and its now working well. Running BIND 9.9.1 and
'haveged' on both machines. I have modified my 'signer' script so if the
zone t
12 matches
Mail list logo
