Symantec Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series, Administration Manual

Page: 143 / 861

143 Establishing your network
About the security gateway’s implementation of DNS
Configuring enclave DNS
If you have an enclave network, or a client behind a security gateway, which is behind a second
security gateway, you must configure a root server record.
Figure 5-13 shows an enclave network. In
this case, you need to configure a root server on security gateway 2, which points to the inside
interface of security gateway 1.
Figure 5-13 Example network layout with an enclave network
When setting up a network to use enclave DNS, configure the following additional record with the
records you configured for the authoritative name server with delegation on the security gateway:
See “Configuring an authoritative name server with delegation” on page 142.
Understanding the security gateway’s DNS resource records
Before you set up the resource records for the security gateway DNS proxy, you need to understand
some of the differences between RFC-defined DNS and the way Symantec has implemented it. While
the security gateway’s DNS implementation and RFC-defined methodologies are similar, the way in
which they store their information is different. The following tables identify the differences between
RFC-defined methodologies and the security gateway’s.
Root server record
(on security gateway 2)
See “Configuring DNS for an enclave network with a DNS root server record” on page 150.
Table 5-2 RFC-defined and security gateway record name comparison
RFC-defined record names Security gateway DNS record names
MX Mail server record
CNAME Host record
PTR Host record
A Host record