This host record is used by the DirectAccess client to verify end-to-end corporate network connectivity over the DirectAccess connection. For multisite deployments there will be directaccess-WebProbeHost A host records for each entry point in the organization. If load balancing is enabled, this host record will resolve to the virtual IP address (VIP) of the array.
It simply compares the IP address returned by the query to the expected address (NAT64 prefix + 7F00:1 or ::1).ĭirectaccess-WebProbeHost – This DNS host record includes only A records and resolves to the IPv4 address assigned to the internal network interface of the DirectAccess server. Note: The DirectAccess client does not attempt to connect to the IP address resolved by directaccess-corpConnectivityHost. If it does not resolve, or resolves to a different address, the client will assume that the transition tunnel was not established successfully and, if possible, fall back to another IPv6 transition protocol and repeat the process until it is successful. ) to an IPv6 address that it expects (the organization’s NAT64 prefix + 7F00:1 or ::1). It does this by attempting to resolve the hostname directaccess-corpConnectivityHost.
This host record is used by the DirectAccess client to determine if name resolution for the corporate namespace is working after the IPv6 transition tunnel (6to4, Teredo, or IP-HTTPS) has been established. When DirectAccess is configured on a network with native IPv6, the directaccess-corpConnectivityHost DNS record will only include a single AAAA record resolving to ::1. Its AAAA host record resolves to an IPv6 address that is a combination of the DirectAccess NAT64 IPv6 prefix and 7F00:1 (the hexadecimal equivalent of 127.0.0.1). Its A host record resolves to 127.0.0.1, which is the IPv4 loopback address. Here is a detailed description for each of these DirectAccess DNS entries.ĭirectaccess-corpConnectivityHost – This DNS host record includes both A and AAAA records when deployed on IPv4-only networks.
DNS ENTRY TO DIRECT URL TO IP WINDOWS 8
These DirectAccess DNS entries are used by Windows 8 and later clients for connectivity checks at various stages of DirectAccess connection establishment.įigure 1 – DirectAccess DNS records for IPv4-only network.įigure 2 – DirectAccess DNS records for dual-stack IPv4/IPv6 network.
One of them is directaccess-corpConnectivityHost and the other is directaccess-WebProbeHost. After installing and configuring DirectAccess with Windows Server 2012 R2, several new host records appear automatically in the internal DNS (assuming dynamic DNS is supported, of course).
0 kommentar(er)
