Google has made my life somewhat difficult lately by encrypting everything if you are logged into a Google account or using encrypted.google.com. The SSL encryption causes my URL and network application filtering appliance to fail miserably at blocking certain types of material that comes up in Google searches that it would normally block on an unencrypted connection.
I have discovered that Google provides a method of forcing Google searches to be unencrypted. That solution can be seen at the following link: http://support.google.com/websearch/bin/answer.py?hl=en&answer=173733.
Part of the solution is to create a CNAME record "www.google.com" that points to “nosslsearch.google.com”; however, I am having trouble figuring out how to successfully accomplish this. If they have their own article on the specific implementation of this record, I have not been able to locate it.
I have a Windows Server 2008 R2 Active Directory forest, with all domain controllers also acting as DNS servers (AD integrated). My understanding is that if I attempt to add a forward lookup zone “google.com” and add the desired CNAME record, my internal DNS servers become authoritative for the google.com domain name. Basically, absent any other resource records in the google.com forward lookup zone in our internal DNS servers, DNS requests for other hosts or subdomains in the google.com domain would simply fail. Examples would be Google Docs and Gmail, which are docs.google.com and mail.google.com, respectively.
Is there some way to configure a Windows Server 2008 R2 SP1 DNS server so that it contains the desired CNAME record but forwards other DNS lookup requests for other hosts/subdomains for google.com to the configured forwarding servers (or at least to the nameservers listed for google.com)?