Re: "broken trust chain" for non-existing AAAA records

2010-11-29 Thread lst_hoe02
Zitat von Mark Andrews : Is this still with BIND 9.7.0-P1 or something more recent? If it is still BIND 9.7.0-P1 then please upgrade. There really is no point debugging validation failures in BIND 9.7.0-P1 anymore as the validator has had really extensive changes since then. Please remember,

Re: zone management plus automatic "nsupdate"

2010-11-29 Thread Chris Buxton
On Nov 28, 2010, at 3:25 AM, Christian Ruppert wrote: > Hey guys, > > we have many zones and a few admins who are able to edit those. Now > we're looking for a good and free solution to a) track who changed what > and b) to update the zone afterwards. > > So we thought using git with a update ho

Re: "broken trust chain" for non-existing AAAA records

2010-11-29 Thread Mark Andrews
Is this still with BIND 9.7.0-P1 or something more recent? If it is still BIND 9.7.0-P1 then please upgrade. There really is no point debugging validation failures in BIND 9.7.0-P1 anymore as the validator has had really extensive changes since then. Please remember, that unlike most of the res

Re: about the zone file management

2010-11-29 Thread Lyle Giese
Or nsupdate Lyle Giese LCR Computer Services, Inc. philippe.simo...@swisscom.com wrote: > Hi > > if i good understand your question maybe the answer is : > rndc freeze / thaw > > Philippe > > > >> -Original Message- >> From: bind-users-bounces+philippe.simonet=swisscom@lists.

Re: "broken trust chain" for non-existing AAAA records

2010-11-29 Thread lst_hoe02
Zitat von Mark Andrews : In message <20101118131400.37717e5p5tard...@webmail.kwsoft.de>, lst_ho...@kwsof t.de writes: We are using Bind 9.7 at the border to resolve DNS queries for a small LAN. After moving forward in using IPv6 we discovered many "broken trust chain" errors in the bind log

find the professional DNS hosting service

2010-11-29 Thread Jorg W Young
Hi list, We are a company running for gaming. Our website's rank is about 500 in Alexa. We didn't have our own nameservers, have been using the domain registry provider's nameservers for free. Due to some problems, we want to change the DNS hosting. The provider should have included the features: