(no subject)

Barry Margolin barmar at bbnplanet.com
Wed Nov 3 16:19:52 UTC 1999


In article <17846.941642723 at kludge.mpn.cp.philips.com>,
Jim Reid  <jim at mpn.cp.philips.com> wrote:
>>>>>> "Xunhua" == Xunhua WANG <xwang4 at gmu.edu> writes:
>
>    Xunhua> We are running BIND 4.97 for NT. Now we plan to upgrade it
>    Xunhua> to BIND822 (for NT).
>
>    Xunhua> How can we port the orignal configuration file to the new
>    Xunhua> BIND? It seems that there are a lot of changes for the
>    Xunhua> configuration: for example, the BIND497 uses
>    Xunhua> c:\winnt\named.boot but BIND822 uses
>    Xunhua> c:\winnt\system32\dns\etc\named.conf, and so on? 
>
>Use the named-bootconf script that's bundled with BIND8. It converts a
>named.boot file to its named.conf equivalent. You'll probably have to
>run this on a UNIX system => transferring the named.boot file from
>your NT box to the UNIX system, creating the named.conf file there and
>copying that back to your NT box.

Why would he have to run it on Unix?  I haven't looked closely at the
program (which is no longer a script, it was rewritten in C in 8.2), but I
can't imagine that it does anything that can't be done in completely
portable C.

-- 
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.


More information about the bind-users mailing list