In message <200911151416.nafeg2n5083...@dc.cis.okstate.edu>, Martin McCormick w
rites:
> Hauke Lampe writes:
> > When BIND writes zone files, it uses $origin to group records that share
> > a common base name. Just "update delete/add" all records and the mixed
> > case $origin disappears.
>
> It
Hauke Lampe writes:
> When BIND writes zone files, it uses $origin to group records that share
> a common base name. Just "update delete/add" all records and the mixed
> case $origin disappears.
It did. Many thanks.
Martin McCormick WB5AGZ Stillwater, OK
Systems Engineer
OSU Information Technol
Hauke Lampe writes:
> $origin is a preprocessor statement. It's not an attribute of a zone, so
> you cannot change it directly.
>
> When BIND writes zone files, it uses $origin to group records that share
> a common base name. Just "update delete/add" all records and the mixed
> case $origin disap
Martin McCormick wrote:
> Is there a way using nsupdate to change a $origin directive in a
> zone file?
$origin is a preprocessor statement. It's not an attribute of a zone, so
you cannot change it directly.
When BIND writes zone files, it uses $origin to group records that share
a common base n
Is there a way using nsupdate to change a $origin directive in a
zone file?
Some months ago, I accidentally loaded a configuration
in to a DHCP server that registered a bunch of private-network
hosts having a domain name of WiFi-ATRC.osu. We really wanted
wifi-atrc.osu. Bind worked properl
5 matches
Mail list logo