...
See Figure 20.1.
| Anchor | ||||
|---|---|---|---|---|
|
| Drawio | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Note: You must also create an A record for the host defined as a mail exchanger in an MX record.
...
When using a DNAME record, you must copy the resource records for the source domain to the zone containing the target domain, so that the DNS server providing service for the target domain can respond to the redirected queries.
| Copy from corpxyz.com | to corpxyz.corp200.com |
|---|---|
| www1 IN A 10.1.1.10 | www1 IN A 10.1.1.10 |
| www2 IN A 10.1.1.11 | www2 IN A 10.1.1.11 |
| ftp1 IN A 10.1.1.20 | ftp1 IN A 10.1.1.20 |
| mail1 IN A 10.1.1.30 | mail1 IN A 10.1.1.30 |
After copying these records to the zone containing the corpxyz.corp200.com domain, delete them from the zone containing the corpxyz.com domain.
If DNS service for the source and target domain names is on different name servers, you can import the zone data from the NIOS appliance hosting the source domain to the appliance hosting the target domain. For information about this procedure, see Importing Zone Data.
If DNS service for the source and target domain names is on the same name server and the parent for the target domain is on a different server, you can delegate DNS services for the target domain name to the name server that provided—and continues to provide—DNS service for the source domain name (see Figure 20.5). By doing this, you can continue to maintain resource records on the same server, potentially simplifying the continuation of DNS administration.
...