Have left as is (for now). Finish the rest off tomorrow... The box runs WHM
/ cPanel... and just holds a few vhosts under single domain. DNS is handled
by ISP's servers...

If anything in original was modified, it was done by WHM/cPanel, not me...

Am at the freebsd-update install point now... so will have another look at
things in the morning with fresh eyes...

Ta fer the suggestions folks!

Marc A Coyles
ICT Support Team (ext 730)
Mbl: 07850 518106


-----Original Message-----
From: Kevin Kinsey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2008 4:16 PM
To: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Subject: Re: Upgrade 6.2-Release to 7.0-Release - stuck!

Marc Coyles wrote:
> Am running freebsd-update following instructions at
>
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.htm
l
>
> It’s decided that it can’t merge named.conf changes automagically and has
> dropped me into vi with the file open… looking as below. What exactly is
it
> wanting me to do? T’isn’t particularly clear, and this is the first time
> I’ve ever attempted an upgrade…

It's [apparently] expecting you to use vi to create a named.conf
that will work, and showing you the contents of both the old
named.conf and the one found in 7.0-RELEASE.  I'm not familiar
with freebsd-update (still using the old csup/buildworld routine)
but it sure look like mergemaster, more or less, except that
mergemaster not only allowed you to leave it until later and
do the merge "by hand" but also had a two-column "diff" with
a selector routine, so you could create a "merged" version
on-the-fly.

Is the box an important DNS server?  What happens if you just
save the file as is and try and come back to it later? (YMMV,
standard disclaimer, and all that).  if you've *never* edited
named.conf before, you'd probably be OK to just remove all the
current version stuff in favor of the 7.0-RELEASE stuff, *but*
generally all my boxen *have* been altered, so that wouldn't
work.

> <<<<<<< current version
> include "/etc/namedb/rndc.key";
>
> controls {
>         inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
> };
>
> // $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27
dougb
> Exp
> $
> =======
> // $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23
dougb
> Exp
> $
>>>>>>>> 7.0-RELEASE
> //
> // Refer to the named.conf(5) and named(8) man pages, and the
documentation
> // in /usr/share/doc/bind9 for more details.
> //
> // If you are going to set up an authoritative server, make sure you
> // understand the hairy details of how DNS works.  Even with
> // simple mistakes, you can break connectivity for affected parties,
> // or cause huge amounts of useless Internet traffic.
>
> options {
> <<<<<<< current version
>         pid-file "/var/run/named/pid";
> =======
>         // Relative to the chroot directory, if any
>>>>>>>> 7.0-RELEASE
>         directory       "/etc/namedb";
>         dump-file       "/var/dump/named_dump.db";
>         statistics-file "/var/stats/named.stats";
>
> // If named is being used only as a local resolver, this is a safe
default.
> // For named to be accessible to the network, comment this option, specify
> // the proper IP address, or delete this option.
>         listen-on       { 127.0.0.1; };
>
> // If you have IPv6 enabled on this system, uncomment this option for
> // use as a local resolver.  To give access to the network, specify
> // an IPv6 address, or the keyword "any".
> //      listen-on-v6    { ::1; };
>
> // These zones are already covered by the empty zones listed below.
> // If you remove the related empty zones below, comment these lines out.
>         disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
>         disable-empty-zone
> "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
> 0.0.0.0.0.0.IP6.ARPA";
>         disable-empty-zone
> "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
> 0.0.0.0.0.0.IP6.ARPA";
>
> // In addition to the "forwarders" clause, you can force your name
> // server to never initiate queries of its own, but always ask its
> // forwarders only, by enabling the following line:
> //
> //      forward only;
> // If you've got a DNS server around at your upstream provider, enter
> // its IP address here, and enable the line below.  This will make you
> // benefit from its cache, thus reduce overall DNS traffic in the
Internet.
> /*
>         forwarders {
>                 127.0.0.1;
>         };
> */
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND versions 8 and later
>          * use a pseudo-random unprivileged UDP port by default.
>          */
>         // query-source address * port 53;
> };
>
> // If you enable a local name server, don't forget to enter 127.0.0.1
> // first in your /etc/resolv.conf so this server will be queried.
> // Also, make sure to enable it in /etc/rc.conf.
>
> // The traditional root hints mechanism. Use this, OR the slave zones
below.
> zone "." { type hint; file "named.root"; };
>
> /*      Slaving the following zones from the root name servers has some
>         significant advantages:
>         1. Faster local resolution for your users
>         2. No spurious traffic will be sent from your network to the roots
>         3. Greater resilience to any potential root server failure/DDoS
>
>         On the other hand, this method requires more monitoring than the
>         hints file to be sure that an unexpected failure mode has not
>         incapacitated your server.  Name servers that are serving a lot
>         of clients will benefit more from this approach than individual
>         hosts.  Use with caution.
>
>         To use this mechanism, uncomment the entries below, and comment
>         the hint zone above.
> */
> /*
> zone "." {
> <<<<<<< current version
>         type hint;
>         file "/etc/namedb/named.root";
> =======
>         type slave;
>         file "slave/root.slave";
>         masters {
>                 192.5.5.241;    // F.ROOT-SERVERS.NET.
>         };
>         notify no;
>>>>>>>> 7.0-RELEASE
> };
> <<<<<<< current version
>
> zone "0.0.127.IN-ADDR.ARPA" {
>         type master;
>         file "/etc/namedb/localhost.rev";
> =======
> zone "arpa" {
>         type slave;
>         file "slave/arpa.slave";
>         masters {
>                 192.5.5.241;    // F.ROOT-SERVERS.NET.
>         };
>         notify no;
>>>>>>>> 7.0-RELEASE
> };
> <<<<<<< current version
>
> // RFC 3152
> zone
> "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA"
> {
>         type master;
>         file "/etc/namedb/localhost-v6.rev";
> =======
> zone "in-addr.arpa" {
>         type slave;
>         file "slave/in-addr.arpa.slave";
>         masters {
>                 192.5.5.241;    // F.ROOT-SERVERS.NET.
>         };
>         notify no;
>>>>>>>> 7.0-RELEASE
> };
> */
>
> /*      Serving the following zones locally will prevent any queries
>         for these zones leaving your network and going to the root
>         name servers.  This has two significant advantages:
>         1. Faster local resolution for your users
>         2. No spurious traffic will be sent from your network to the roots
>
>
> (no other <<<current or >>>>7.0-RELEASE beyond this point…
>
> Marc A Coyles
> ICT Support Team (ext 730)
> Mbl: 07850 518106

Good luck,

Kevin Kinsey

--
The three best things about going to school are June, July, and August.




_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to