688
edits
Changes
Jump to navigation
Jump to search
Line 328:
Line 328: − + − − This could be used to direct DNS for a domain to an internal DNS server connected to your network using a VPN or a custom route. Line 342:
Line 340: − Note that 'domain-remote' entries do not appear in server-manager, and can be managed only from the command line.+ +
SME Server:Documentation:FAQ:Section01 (view source)
Revision as of 12:31, 29 June 2016
, 12:31, 29 June 2016Add note that Nameservers can be a comma delimited list
===DNS Forwarding===
===DNS Forwarding===
The dnscache service can be configured to forward all queries for a specific domain to an alternate server using the "domain-remote" record type in the domains db
The dnscache service can be configured to forward all queries for a specific domain to an alternate server using the "domain-remote" record type in the domains db. This could be used to direct DNS for a domain to an internal DNS server connected to your network using a VPN or a custom route, or to direct your local active directory DNS to your Active Directory server, etc.
To forward all DNS for <domainname> to a specified remote DNS server (4.2.2.1 in this example):
To forward all DNS for <domainname> to a specified remote DNS server (4.2.2.1 in this example):
db domains set <domainname> domain-remote Nameservers 4.2.2.1
db domains set <domainname> domain-remote Nameservers 4.2.2.1
signal-event domain-modify
signal-event domain-modify
As a side-effect, you can block DNS for a domain by configuring DNS forwarding to 'localhost'.
As a side-effect, you can block DNS for a domain by configuring DNS forwarding to 'localhost'.
signal-event domain-modify
signal-event domain-modify
* 'domain-remote' entries do not appear in server-manager; they can be managed only from the command line.
* Nameservers can be a comma-delimited list of servernames or IP addresses
==Virus Scanning==
==Virus Scanning==