Upgrading BIND4 to BIND8 on OpenBSD

[peter at icke-reklam.manet.dot..nu]

Francis Bustamante <fbusta1 at gl.umbc.edu> wrote:
> I've decided to let go of redhat on sparc and go with OpenBSD.
> OpenBSD 2.6 ships with BIND4 installed.  I tried to get the
> ports collection and do a 

> root at sparkle [/usr/ports/net/bind8] -> make

> then

> root at sparkle [/usr/ports/net/bind8] -> make install

> when I try to restart, it still reads named.boot (BIND 4).
> Am I missing a step here?

Yes, your bind4 might be left on disk and located before bind8 in the path.

Openbsd installs bind4 in it's native "base distribution" so ther's no
package to remove. You have to identify named (/usr/sbin/named) 
ndc (/usr/sbin/ndc) named-xfer (/var/named/named-xfer) and remove them
manually. 

Then make install will install bind8.

Peter h

> Thanks,
> Francis

> On Thu, 13 Apr 2000, Kevin Darcy wrote:

>> You still haven't provided the specifics of the problem, so I'm limited to
>> speculation and guessing.
>> 
>> My best guess is that you recently changed nameservers and it took a while for
>> the glue-record change to propagate to all of the root servers. Why do I think
>> it's a glue-record that you looked up? Because, except for glue records, root
>> servers would normally only give referrals as responses to A record queries.
>> 
>> 
>> - Kevin
>> 
>> marky wrote:
>> 
>> > Yes, I got a bad A record. There were no delegations. I queried
>> > A.ROOT-SERVERS.NET and got back the wrong info.
>> > whois lists my nameserver. My nameserver has the correct info. My ISP's name
>> > server has the correct info.
>> > My questions is, how could this happen, and how do I correct it? If the info
>> > at NSI is correct, and my name server is
>> > correct, how could the wrong info get out there?
>> >
>> > "Kevin Darcy" <kcd at daimlerchrysler.com> wrote in message
>> > news:38ED0776.9C7C636D at daimlerchrysler.com...
>> > > Okay, this is getting confusing. You say that you followed the delegations
>> > and
>> > > got a bad A record. And you say that WHOIS lists your nameserver. So, did
>> > you
>> > > get the bad A record from your nameserver? Apparently not, since you say
>> > the
>> > > information is correct on your nameserver. Did you get the bad A record
>> > from
>> > > some server that is providing secondary service for your domain? Then talk
>> > to
>> > > them. Or did the delegations not match the WHOIS record? Then take that up
>> > with
>> > > NSI. Or perhaps the *name* of your server is correct in the
>> > > delegation/WHOIS record, but the *address* associated with that name is
>> > wrong.
>> > > If that's the case, then submit a host record update to NSI.
>> > >
>> > > If you had actually told us what name you were having a problem with, what
>> > > address it should be pointing to, and what the address of your server is,
>> > we
>> > > probably could have already pinpointed where the problem lies. But, since
>> > you
>> > > have chosen not to, we're still at the guessing and speculation stage...
>> > >
>> > >
>> > > - Kevin
>> > >
>> > > marky wrote:
>> > >
>> > > > Thanx! It returns an A record, and that A record is wrong. But the
>> > > > information is correct on our nameserver,
>> > > > and a network solutions whois is pointing to our server. In this case,
>> > who
>> > > > do you contact to find out what
>> > > > is happening?
>> > > >
>> > > > "Barry Margolin" <barmar at bbnplanet.com> wrote in message
>> > > > news:3KNE4.15$YN6.1296 at burlma1-snr2...
>> > > > > In article <6LBE4.89622$8k3.756355 at news1.rdc1.sdca.home.com>,
>> > > > > Marky <markyh at home.com> wrote:
>> > > > > >Dan - thanx for the tip. I noticed that the root servers are also
>> > caching
>> > > > > >the wrong data.
>> > > > >
>> > > > > The root servers are non-caching servers, so anything they have should
>> > > > come
>> > > > > from the WHOIS database.  If they have a wrong A record, you must have
>> > the
>> > > > > host registered in WHOIS.
>> > > > >
>> > > > > >I'm beside myself here, how do I follow a delegation path? Sorry for
>> > a
>> > > > > >simple question,
>> > > > >
>> > > > > dig <name> a @<server> +norecurse
>> > > > >
>> > > > > where <name> is the fully-qualified name that you're trying to look
>> > up,
>> > > > and
>> > > > > <server> is the server name in the delegation (start with
>> > > > > a.root-servers.net).  If it returns the A record, you've completed the
>> > > > > process; if it returns a bunch of NS records, query them similarly.
>> > > > >
>> > > > > --
>> > > > > Barry Margolin, barmar at bbnplanet.com
>> > > > > GTE Internetworking, Powered by BBN, Burlington, MA
>> > > > > *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to
>> > > > newsgroups.
>> > > > > Please DON'T copy followups to me -- I'll assume it wasn't posted to
>> > the
>> > > > group.
>> > > > >
>> > > > >
>> > > > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> 
>> 
>> 
>> 
>> 





-- 
--
Peter Håkanson         
        Manet Networking      (At the Riverside of Gothenburg, home of Volvo)
           Sorry about my e-mail address, but i'm trying to keep spam out.
echo "peter (at) manet (dot) nu" | sed "s/(at)/@/g " | sed "s/(dot)/\./g"|sed "s/ //g"