First of all, decide where you want the delta to be computed. On
the master or on the slaves? Currently you are asking all servers
to compute the delta.
Secondly if you are not using dynamic update to modify the master
zone you don't need to freeze the master zone as named is NOT writing
to it.
In message , seren writes:
>
> Thanks for your response. I didn't know about the +trace option in dig. =
> After some more searching, I believe you are correct about the long =
> responses being related. The responses that fail all seem to exceed =
> 512-bytes. Why this would happen in multiple l
Hi folks,
According to DNS and BIND (the book) and other sources, BIND from 9.3 on
is able to calculate differences for a zone file that is manually edited
by using the following methodology:
rndc freeze
perform-updates-on-the-zone-file
rndc thaw
http://books.google.com/books?id=HggtWI1Shv
Thank you very much for your bug report. For your
information, you can also submit bugs to our bind9-bugs
AT isc.org email address. Your issue is now being
tracked as ticket # 20923.
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.
In message <6b845b73-065f-4e8b-afa5-408ecdbe7...@govnet.state.vt.us>, David Kre
indler writes:
> We have BIND 9.6.1-P3 running on several AIX 5.3 servers. On one of them, nam
> ed is filling /var/adm/wtmp with numerous entries like the following.
This is not named (the program). It may be "su" o
On 1/21/10 3:40 PM, Ryan S wrote:
So my setup has been working great modifying existing zones adding
and removing records. But when I add a new zone, it apparently does
not work. So I think I am missing an important file that lists all
the zones BIND uses? What BIND file am I needing to copy
We run 2 BIND in master/master configuration in two geographically separate
datacenters. This is done because a master/slave configuration has certain
limitations if the master goes down (slave can not be easily modified).
The setup we have works great -- we make changes to "A" or "MX" reco
Thanks for your response. I didn't know about the +trace option in dig. After
some more searching, I believe you are correct about the long responses being
related. The responses that fail all seem to exceed 512-bytes. Why this would
happen in multiple locations is a mystery but perhaps our fire
We have BIND 9.6.1-P3 running on several AIX 5.3 servers. On one of them, named
is filling /var/adm/wtmp with numerous entries like the following.
user pts/1 pts/1 7 1327240 1264089183 host-NN.domain Thu Jan 21
10:53:03 EST 2010
named 8 2572472 1264089217
I agree - we are removing 1/2 the masters in a couple weeks to help
things. Slaves only talk to masters, there are no "slaves of slaves"
as we refer to them. Our architecture goal has been uniformity among
the configurations, and this is part of the price we pay for that.
At a functional level,
10 matches
Mail list logo