Synopsis: Named.conf vs named.boot
State-Changed-When: Tue May 4 11:16:03 PDT 1999
Whomever sent this can go and use Windows.
>Synopsis: Named.conf vs named.boot
>State-Changed-When: Tue May 4 11:16:03 PDT 1999
>Whomever sent this can go and use Windows.
Go buy the bind book, third edition. It covers the transition in
Just my Opnion
John C. Place
CTC Distribution Direct - York, PA
I am trying to create named.conf from named.boot by running
the script /etc/named.d/named-bootconf.sh.
We were using SCO 3.2v4.2 but upgraded to SCO 3.2v5.0.5
5.0.5 uses BIND 8.x, and we were required to convert named.boot
to named.conf by using the conversion script described above.
The file named.conf is created, but it appears empty, except for
Does anyone know why?
We were using named.boot under BIND 4.x.
To use BIND 8.x, our named.boot file must be converted to named.conf.