[SUMMARY]: named: xfrnets - "mask problem"

From: Irene A. Shilikhina <irene_at_alpha.iae.nsk.su>
Date: Wed, 20 Jan 1999 11:22:47 +0600 (NSK)

Hello Managers,

yesterday I wrote that including in the xfrnets option (named.boot file)
host addresses instead of network ones gave the warning messages in the
daemon.log file "mask problem" during restart of named.

Thanks to those who answered:

steinberg_at_acphyz.physik.rwth-aachen.de (Rolf Steinberg)
Arrigo Triulzi <arrigo_at_albourne.com>
mike_at_matthews.net (Michael Matthews)
Ian Mortimer <ian_at_physics.uq.edu.au>

Ian Mortimer gave the solution:

>If you want to specify a network you just put in the IP number:
>
> xfrnets xxx.0.0.0 ;for class A
> xfrnets xxx.xxx.0.0 ;for class B
>
>If you want to specify down to a host name you must enter it as
>(example taken from book "DNS and BIND"):
>
> xfrnets 15.255.152.4&255.255.255.255
>
>Or for a subnet:
>
> xfrnets 128.32.1.0&255.255.255.0

I followed this advice and now the xfrnets line looks like:

xfrnets 193.124.36.33&255.255.255.255 212.20.31.125&255.255.255.255

and restart is smooth.

Ian also replied on my question about the book:

>I was using the 2nd edition of the book but the latest is
>
> DNS and BIND, 3rd Edition
>
> By Paul Albitz & Cricket Liu
> 3rd Edition September 1998
> 1-56592-512-2, Order Number: 5122
> 502 pages
>
>You can get more details at http://www.oreilly.com/catalog/dns3/

My special greetings to you, Ian!

Irene

*************************************************************************
* *
* Irene A. Shilikhina e-mail: irene_at_alpha.iae.nsk.su *
* System administrator, *
* Institute of Automation & Electrometry, *
* Siberian Branch of Russian Academy of Sciences, *
* Novosibirsk, Russia *
* http://www.iae.nsk.su/~irene *
*************************************************************************
* * *
* The road to hell is paved with * Every cloud has a silver lining. *
* good intentions. * *
* * *
*************************************************************************

On Tue, 19 Jan 1999, Irene A. Shilikhina wrote:

>
> Hello Everyone,
>
> having added the xfrnets option to the named.boot file with the addresses
> of our secondary Name Servers and restarted named daemon, I got such lines
> in daemon.log file:
>
> Jan 19 15:50:29 alpha named[246]: reloading nameserver
> Jan 19 15:50:30 alpha named[246]: xfrnets element (212.20.31.125) mask
> problem (212.20.31.0)
> Jan 19 15:50:30 alpha named[246]: xfrnets element (193.124.83.69) mask
> problem (193.124.83.0)
> Jan 19 15:50:30 alpha named[246]: Ready to answer queries.
>
> An extract from the documentation:
>
> XFRNETS (origin: Paul Vixie of Digital)
> enables the "xfrnets" command in named.boot. this has the same
> syntax as "forwarders" and "sortlist" -- that is, a list of dotted quads.
> each one is a network (16.0.0.0 and 130.180.0.0 are examples) or a host.
> ^^^^^^^^^
> Nevertheless, replacing the host addresses with the network's ones
> (xxx.xxx.xxx.0) provided a smooth restart:
>
> Jan 19 16:21:13 alpha named[246]: reloading nameserver
> Jan 19 16:21:13 alpha named[246]: Ready to answer queries.
>
> Can anyone explain it?
>
> Thanks,
> Irene
>
Received on Wed Jan 20 1999 - 05:24:42 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT