Page Comparison

...

See Figure 20.1.

Anchor
bookmark1868 bookmark1868

Figure 20.1 MX Records

Drawio
falsewidth border true1 viewerToolbar true fitWindow baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.1 simpleViewer false zoom 1 pageId 22251444 custContentId 7935576 lbox 1 contentVer 1 revision 1

...

Note: You must also create an A record for the host defined as a mail exchanger in an MX record.

...

You can add CNAME records to an IPv4 reverse-mapping zone to create aliases to addresses maintained by a different name server when the reverse-mapping zone on the server is a delegated child zone with fewer than 256 addresses. This technique allows you to delegate responsibility for a reverse-mapping zone with an address space of fewer than 256 addresses to another authoritative name server. See Figure 20.2 and RFC 2317, Classless IN-ADDR.ARPA delegation.

Anchor
bookmark1881 bookmark1881

Figure 20.2 CNAME Records in a Reverse-Mapping Zone

Drawio
width border true1 viewerToolbar true fitWindow false baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.2 simpleViewer false zoom 1 pageId 22251444 custContentId 7083361 lbox 1 contentVer 1 revision 1

You add CNAME records in the parent zone on your name server. The aliases defined in those CNAME records point to the addresses in PTR records in the child zone delegated to the other server.
When you define a reverse-mapping zone that has a netmask from /25 (255.255.255.128) to /31 (255.255.255.254), you must include an RFC 2317 prefix. This prefix can be anything, from the address range (examples: 0-127, 0/127) to descriptions (examples: first-network, customer1). On a NIOS appliance, creating such a reverse-mapping zone automatically generates all the necessary CNAME records. However, if you need to add them manually to a parent zone that has a child zone with fewer than 255 addresses.

...

Anchor
bookmark1884 bookmark1884

Figure 20.3 Adding DNAME Records for the Lowest Level Subdomains
 

Drawio
border true1 viewerToolbar true fitWindow false baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.3 zoom 1 simpleViewerpageId false22251444 widthcustContentIdrevision 7345680 2

In the case

lbox 1 contentVer 1 revision 2

In the case of a domain structure consisting of a single domain (no subdomains), adding a DNAME record redirects queries for every name in the domain to the target domain, as shown in Figure 20.4.

Anchor
bookmark1885 bookmark1885

Figure 20.4 Adding a DNAME Record for a Single Domain

Drawio
falsewidth border true1 viewerToolbar true fitWindow baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.4 simpleViewer false zoom 1 pageId 22251444 custContentId 7935582 lbox 1 contentVer 1 revision 1

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.

...

Anchor
bookmark1886 bookmark1886

Figure 20.5 Making the Target Zone a Delegated Zone<place for figure>

Drawio
border 1 baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.5 zoom 1 pageId 22251444 custContentId 7083355 lbox 1 contentVer 1 revision 1

Note: This is a conceptual representation of domain name mapping and depicts the resulting hierarchical relationship of corp200.com as the parent zone for corpxyz.corp200.com. The hosts are not physically relocated.

...

You might also use DNAME records if you have a number of multihomed appliances whose IP addresses must be mapped to a single set of domain names. An example of this is shown in Figure 20.6.

Anchor
bookmark1887 bookmark1887

Figure 20.6 DNAME Records to Simplify DNS for Multihomed Appliances<place for figure>

Drawio
border 1 baseUrl https://infoblox-docs.atlassian.net/wiki diagramName 20.6 zoom 1 pageId 22251444 custContentId 7083367 lbox 1 contentVer 1 revision 1

...

Note: If you specify a subdomain in the Domain Name field when configuring a DNAME record, and the subdomain is also a subzone, the DNAME record appears in the list view for the subzone, not in the list view for the parent zone that was selected when adding it.

...

A NAPTR (Name Authority Pointer) record specifies a rule that uses a substitution expression to rewrite a string into a domain name or URI (Uniform Resource Identifier). A URI is either a URL (Uniform Resource Locator) or URN (Uniform Resource Name) that identifies a resource on the Internet.
NAPTR records are usually used to map E.164 numbers to URIs or IP addresses. An E.164 number is a telephone number, 1-555-123- 4567 for example, in a format that begins with a country code, followed by a national destination code and a subscriber number. (E.164 is an international telephone numbering system recommended by the International Telecommunication Union.) Thus, NAPTR records allow us to use telephone numbers to reach devices, such as fax machines and VoIP phones, on the Internet.
To map an E.164 to a URI, the E.164 number must first be transformed into a domain name. ENUM (E.164 Number Mapping) specifies a method for converting E.164 numbers to domain names. For example, using the method specified by ENUM, the telephone number 1-555-123-4567 becomes the domain name 7.6.5.4.3.2.1.5.5.5.1.e164.arpa. For details about ENUM, refer to RFC 3761, The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM).
After the E.164 number is converted to a domain name, a DNS client can then perform a DNS lookup for the NAPTR records of the domain name. The following example illustrates how a DNS client processes NAPTR records.
In this example, the telephone number 1-555-123-4567 is converted to the domain name 7.6.5.4.3.2.1.5.5.5.1.e164.arpa. The DNS client then sends a query to the Infoblox DNS server for the NAPTR records associated with 7.6.5.4.3.2.1.5.5.5.1.e164.arpa. The Infoblox DNS server returns the following NAPTR record:

Drawio
border true1 viewerToolbar true fitWindow false baseUrl https://infoblox-docs.atlassian.net/wiki diagramName Managing_NAPTR_Records simpleViewer true width 800 width 800 zoom 1 simple 1 pageId 22251444 custContentId 8656184 lbox 1 contentVer 1 revision 34

The DNS client then examines the fields in the NAPTR record as follows:

...

1. Perform a global search to retrieve the record you want to delete.
   or
   From the Data Management tab, select the DNS tab, click the Zones tab-> dns_view -> zone -> host_record or resource_record.
2. Select the record and click the Delete icon.
3. In the Delete Confirmation dialog box, select Yes to delete or No to cancel.
4. Optionally, if the Enable PTR record removal for A/AAAA records option is selected and if you try to delete an A or AAAA record, the appliance displays the Delete Confirmation (A or AAAA Record) dialog box to confirm whether you want to remove the corresponding PTR record that was automatically generated while creating the A or AAAA record. In the Delete Confirmation dialog box, select the Remove associated PTR resource record(s) check box and click Yes to delete the associated PTR record or click No to cancel. For information about enabling this option, see Deleting PTR Records associated with A or AAAA Records.
   or
   You can also schedule the deletion for a later time. Click Schedule Deletion and in the Schedule Change panel, enter a date, time, and time zone. For information, see Scheduling Deletions.