|-Help||Provide some help with using the dns-ng program.|
|-VERSion||Print the version of the dns-ng program being executed.|
|-Group name pattern|
|In addition to one netgroup for each host, a netgroup of the given name will be created for all hosts with a second HINFO field matching the given pattern. This option may be specified more than once. The first pattern match found is used, machines are not placed in more than one of these groups. Patterns are regular expressions.|
|This option may be used to delete A and NS records which reference names in domains outside the domain specified in the closest preceeding SOA record.|
This option may be used to set the search path for include files.
The idea is that you have all of the information concerning each computer in the one file. This makes it less likely that something will be omitted, and simpler to change if the name or IP address changes.
By using netgroups, you can assign NFS mount permissions (the /etc/exports file) and rlogin permissions (the /etc/hosts.equiv file) based on the kind of machine they are.
Given a database file called example.com and which contains the following textYou can generate the /etc/netgroup file using the following command
Here is what you would see as the output% dns-ng example.com /etc/netgroup \ -g pc MSDOS -g mac MacOS \ -g unix UNIX -g other .* %Note that the output uses relative names.
All of this can be automated using the following makefile fragment:By doing this, all you need to do is edit the example.com file, and the use the make(1) command to bring everything up-to-date./etc/netgroup: example.com dns-ng example.com $@ -g pc MSDOS \ -g mac MacOS -g unix UNIX -g other .*
If you were using NIS, NIS+ or LDAP you would update them, rather than the static file, especially since on many systems the static file doesnt do anything.
|Reference Manual||DNS-NG (1)||dnsutl|