> You could also just edit /var/named/boot.{zones,options} as before and then
> use the command named-bootconf to automatically convert them to the new
> syntax.
Yep, that did the trick :-)
Muchas gracias
Stef
On Tue, Sep 15, 1998 at 01:12:31PM +0100, Oliver Thuns wrote:
> >I made a new install. Debian 1.3.1 is running on another machine.
>
> Dann ist alles klar :-)
>
> >I ran bindconfig, which created a new /etc/named.conf file, but also a
> >new /var/named/boot.options file without all the zones name
Stef Hoesli Wiederwald <[EMAIL PROTECTED]> writes:
>
>Under Debian 1.3.1 I just had a /etc/named.boot file. In Debian 2.0
>ther is now also a more complicated looking /etc/named.conf file, and
>guess what, my nameserver is not serving the zones it should be
>primary for anymore. I guess this is jus
>I made a new install. Debian 1.3.1 is running on another machine.
Dann ist alles klar :-)
>I ran bindconfig, which created a new /etc/named.conf file, but also a
>new /var/named/boot.options file without all the zones named should
>act as primary server for. So I mved /var/named/boot.options.old
> The primaries are configured in named.conf with a new syntax (primary
> is now master). If you now run bindconfig, your old zones will be put
> in named.conf.
No, I ran bindconfig once more, and ended up with the same result as before...
Stef
> Did you update or make a new install?
I made a new install. Debian 1.3.1 is running on another machine.
> I guess on 1.3.1 you used bin
> 4.x.x and now 8.x.x. They have different configuration files. If you
> put your old configuration and zonefiles in /var/named, you could run
> bindconfig to
>Under Debian 1.3.1 I just had a /etc/named.boot file. In Debian 2.0
>ther is now also a more complicated looking /etc/named.conf file, and
>guess what, my nameserver is not serving the zones it should be
>primary for anymore. I guess this is just a RTFM issue. So could
>someone please tell me whic
7 matches
Mail list logo
