Technical References

Specifies whether you want round-robin cycling of equivalent
records in responses to queries. Equivalent records are records
of the same name and type. Since clients often only look at the
first record of a set, enabling this features can help balance
loads and keep clients from forever trying to talk to an
out-of-service host.
save-negative-cache-entries bool default = enabled
Controls whether to have the server store negative query results.
Default, true (enable).
Disabling this feature prevents persistent caching of negative
query responses.
scvg-ignore-restart-interval rangetime(2h-24h) default = 2h
Ensures that the server does not reset the scavenging time with
every server restart. Within this interval, Network Registrar
ignores the time between when a server went down and its restart.
This interval is normally short. The value can range from two
hours to one day. With any time longer than that set,
Network Registrar recalculates the scavenging period
to allow for record updates that cannot take place while the
server is stopped. You can also set this attribute on a zone,
and the value set on the zone overrides the server setting.
Default is 2h.
scvg-interval rangetime(60m-1y) default = 1w
Sets the seconds that DNS waits before removing (scavenging)
out-of-date address (A) records.
scvg-no-refresh-interval rangetime(60m-1y) default = 1w
Sets the number of seconds during which DNS updates cannot increment
the zone timestamp.
scvg-refresh-interval rangetime(60m-1y) default = 1w
Sets the number of seconds during which DNS updates can increment
the zone timestamp. After both the no-refresh and refresh intervals
expire, the record is a candidate for scavenging. The value
can range from one hour to 365 days. The zone setting overrides
the server setting of 604800s (1w).
simulate-zone-top-dynupdate bool default = disabled
Enables compatibility with a Windows 2000 Domain Controller.
When processing a dynamic update packet, which attempts to add
or remove A records from the name of a zone, DNS responds as if
the update succeeded, rather than responding with a refusal, as
would normally occur due to the protected/unprotected name
conflict. No update to the records at the zone name will actually
occur, although the response indicates that it has.
slave-forward-retry-time rangetime(5s-60s) default = 10s