HP 635n HP Jetdirect Print Servers - Practical IPv6 Deployment for Printing an - Page 13

Figure 7 - ADI DNS Here we are formally introducing Active Directory. We'll assume the domain name is "example.internal" and that all Microsoft servers and workstations are part of the domain. Active Directory Integrated DNS (ADI-DNS) is where the DNS database is stored in Active Directory. For devices that are integrated into the Active Directory, ADI-DNS allows for a secure update to DNS using a kerberized DNS update mechanism. Devices that are not integrated into the Active Directory either use WINS or ask the DHCPv4 server to update DNS on their behalf. A typical network setup would be that the DHCPv4 supplies the DNS server address, the domain name, and the router IP addresses to the two subnets shown in Figure 7. Upon receiving this information from the DHCPv4 server, the Vista systems can update DNS. The HP MFPs ask the DHCPv4 server to update DNS on their behalf and if a WINS server is provided in the DHCPv4 configuration, the HP devices will register their names with the WINS server too. In the DNS database for the zone "example.internal", something like the following would probably be seen: • vista1 A • vista2 A • mfp1 A • mfp2 A 192.168.1.21 192.168.1.22 192.168.1.23 192.168.2.100 // added to DNS by Vista1 // added to DNS by Vista2 // added to DNS by the DHCPv4 Server // added to DNS by the DHCPv4 Server Essentially, vista1.example.internal will map to 192.168.1.21, vista2.example.internal will map to 192.168.1.22, and so on. These mappings are stored in what is called an "A" record. DNS can also hold name to IPv6 address mappings through an AAAA record. The same name, such as "vista1", can have multiple A records and multiple AAAA records associated with it. Notice the no IPv6 records are present - this is because the only IPv6 addresses available are Link Local addresses. Vista will not register Link Local addresses in DNS and neither should you because Link Local addresses are only valid for their subnet and a name to address mapping could be returned to a device on another subnet. This would result in communication errors and timeouts. In addition, Microsoft also recommends not adding Link Local addresses to the hosts file either. Once we have introduced DNS into our infrastructure, we now have two commonly used names that can be used to identify devices. One is to use the hostname and the other is to use a Fully Qualified Domain Name or FQDN (Note: technically an FQDN ends in a period - such as "mfp2.example.internal.", but the term FQDN is commonly used in the way described here). Here are the examples: 13