DNS decoupling resolves the same domain name for the intranet to be resolved to a different IP address.
The main point is to provide different domain name resolution records according to different clients.
Some e-commerce sites in the real-time network in order to let users have a better experience of the resolution faster, the user from different operators to resolve to the corresponding server so that greatly improve the access speed.
This is configured directly with a built-in DNS server
A detailed tutorial is available in the previous article in the building of DNS: http://blog.51cto.com/13630803/2114574
1: Edit configuration file named.conf
Listen-on Port: (any;}; Set to any to listen on all addresses and ports
allow-query {any;}; Set to any to allow all network segments to use DNS
2: Find 37 lines 4DD cut down and paste into the Named.rfc1912.zones file later
3: Edit/etc/named.rfc1912.zones
Forward parsing and reverse parsing in the configuration intranet
Configuring forward parsing for external networks
4: Open Directory/var/named
Copy named.localhost named Benet.com.zone.lan
Copy named.localhost named Benet.com.zone.wan
Edit Benet.com.zone.lan
5: Edit Benet.com.zone.wan
6: Edit resolv.conf
Add DNS server address
7: Open named Service
8: Test with 2 sets of Win7
Set the Win7 address 12.0.0.10 and DNS server 12.0.0.1
DNS resolution for test extranet
9: Set the address of another Win7 192.168.100.77 DNS server 192.168.100.1
Analysis of Test Intranet
DNS Separation resolved successfully
DNS split resolution configuration in Linux redhat6.5