@lbutlr wrote:
>
> The latest surprise was that dnssec-enable yes; is obsolete in Bind 9.16.
`dnssec-enable yes` has been the default since 2007, so that directive has
been useless for quite a long time :-) What changed in 9.16 is that you
now can't turn DNSSEC off. (Specifically, support for
On 06 Jul 2020, at 17:59, Mark Andrews wrote:
> Nsupdate can normally determine the name of the zone that has to be updated
> so most of the time you don’t need to specify the zone. There are a few
> cases, like when adding delegating NS records or glue to the parent zone you
> have to
Actually you had "zone name covisp.net” which told nsupdate to update the
“name.” zone as it was treated as “zone name”. Nsupdate then when and looked
up the SOA for name and found ac1.nstld.com is the primary server.
name. 86400 IN SOA ac1.nstld.com.
On 06 Jul 2020, at 16:47, Kevin Darcy wrote:
> You didn't dot-terminate covisp.net in the "zone" statement
Ow!
Sigh.
--
The whole thing that makes a mathematician's life worthwhile is that
he gets the grudging admiration of three or four colleagues
[ Classification Level: GENERAL BUSINESS ]
You didn't dot-terminate covisp.net in the "zone" statement, so it may be
appending who-knows-what to one of its queries, and going awry.
nsupdate -d (or -D) shows all :-)
- Kevin
On Mon, Jul
Trying to verify that I can make changes with nsupdatem and running into
something I don’t understand.
mail # nsupdate -k admin.key
> zone name covisp.net
> update delete ns1.covisp.net. INA 65.121.55.42
> update add ns1.covisp.net. 3601 INA 65.121.55.42
> send
;
6 matches
Mail list logo
