Jump To: Support > KB > NetManager > Network > DNS

DNS

NetManager as primary (authoritative) server

By default NetManager will be authoritative for the internal domain. This is enabled by domain_internal_master="y" in the configuration file.

The internal domain is specified by domain_internal.

Secondary servers can be domain_internal_secondary in the format servername,IP-address e.g. domain_internal_secondary="dc01,10.0.0.2"

NetManager as a member (caching only) server

Set domain_internal_master="n" and then set domain_internal_primary to a space-separated list of the primary servers

Looking up external DNS

You may either set dns_external to a space-separated list of external DNS servers (e.g. dns_external="8.8.8.8 8.8.4.4") or set dns_rootservers="y" for NetManager to resolve everything itself using the global root nameservers.

The internal will still be looked up either from itself (if authoritative) or from the specified internal servers (set with domain_internal_primary).

Additionally, specific domains/hosts can be looked up from a given IP address using dns_forwarder_domains which is a list of domain,IP-address pairs such as dns_forwarder_domains="mmx-ds.cdn.whatsapp.net,8.8.8.8 mmg.whatsapp.net,8.8.8.8 mms.whatsapp.net,8.8.8.8 media-lhr3-1.cdn.whatsapp.net,8.8.8.8"

Additional domains

If you want to run DNS for any other arbitrary domains, you can use dns_master_domains to specify them. You will need to hand-write your own BIND zone file. The variable format is as follows: dns_master_domains="myschool.local,myschool.local.zone:update". This creates a zone for myschool.local using the zone file myschool.local.zone and allows dynamic updates.