Hi list,
Is it ok to upgrade from 9.4.2 to 9.7.0-P2 directly?
i mean i already have 9.4.2, i can install latest one with ./configure, make
and make install, is there a problem with this steps?
please note i already tried it and it worked fine on a cache-only DNS.
regards,
Sasa
Warren Kumari
--
Please excuse typing, etc -- This was sent from a device with a tiny
keyboard.
On Jun 13, 2010, at 9:15 AM, sasa sasa wrote:
Hi list,
Is it ok to upgrade from 9.4.2 to 9.7.0-P2 directly?
Yup, no worries...
i mean i already have 9.4.2, i can install latest one w
Hello,
I'm seeing an unfamiliar error while attempting to start a newly built from
source named instance. I've search on the net and within the bind-user list
without luck, DST returns lots of hits, but nothing with "named DST".
hoping someone here might know what its about. Is it real
sorry, forgot the subject. not very good on my first posting
Hello,
I'm seeing an unfamiliar error while attempting to start a newly built from
source named instance. I've search on the net and within the bind-user list
without luck, DST returns lots of hits, but nothing with "named D
On 06/13/10 06:15, sasa sasa wrote:
Hi list,
Is it ok to upgrade from 9.4.2 to 9.7.0-P2 directly?
Yes, but you should do some testing before you install the new version
on your live, production system. There are some differences in the
defaults for named.conf, and when upgrading to a new ver
On 06/11/10 02:51, John Marshall wrote:
BIND 9.7.1rc1
FreeBSD 8.1-PRERELEASE
I've just stepped into the world of nsupdate (instead of doing the
freeze/edit/thaw dance). I have had success using TSIG (nsupdate -k)
but I would like to use TKEY-GSS (nsupdate -g). When I try to do that,
nsup
Recently, I implemented an instance of BIND that provides a "tailored" name
services for a private network connection between two organization. This
instance of BIND returns responses for a limited portion of our internal name
and address space that the other organization is permitted to access
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
work in a Windows 7 environment after a decision is made to upgrade Windows?
In the past I've instal
On Jun 13, 2010, at 1:08 PM, Doug Barton wrote:
> On 06/13/10 13:00, Merton Campbell Crockett wrote:
>> Microsoft's nslookup is broken. What alternative applications that can
>> be installed and used in a Windows XP environment that will continue to
>> work in a Windows 7 environment after a dec
On 06/13/10 14:08, Merton Campbell Crockett wrote:
On Jun 13, 2010, at 1:08 PM, Doug Barton wrote:
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
At Tue, 8 Jun 2010 11:03:55 +0200,
Torsten wrote:
> Everything works perfectly okay except queries for
> 1.0.0.127.in-addr.arpa and 0.0.0.0.in-addr.arpa. These are refused by
> the caching server (denied entries in default log).
> Asking those queries on an identical server without views returns
On Jun 13, 2010, at 2:21 PM, Doug Barton wrote:
>> The problem with the erroneous functioning of Microsoft's nslookup.exe
>> is that it requires a corporate wide change. There are a number of
>> reasonably intelligent users that assume nslookup.exe is providing them
>> correct information. I woul
On 06/13/10 15:55, Merton Campbell Crockett wrote:
Providing access to the web-based tools to IT personnel might not be
that big of a challenge;
Excellent!
however, the problem remains: Using "nslookup"
is an ingrained behavior for the general user.
I would assert that "the general user" h
Am Sun, 13 Jun 2010 14:45:22 -0700
schrieb JINMEI Tatuya / 神明達哉 :
> At Tue, 8 Jun 2010 11:03:55 +0200,
> Torsten wrote:
>
> > Everything works perfectly okay except queries for
> > 1.0.0.127.in-addr.arpa and 0.0.0.0.in-addr.arpa. These are refused
> > by the caching server (denied entries in def
14 matches
Mail list logo