>  or by a hostname that is aliased to www.mygooglemapssite.com using a
>  DNS CNAME record."

It says aliased *to*, not *for*.

So it doesnt matter if www.publico.es is a CNAME for something else.
You should still be able to access the site.

What you wont be able to do is visit the site as
http://www.publico.es.edgesuite.net/ but persumably nobody ever does
that so you should be fine.

The key is locked to the domain seen by the visitor and the browser -
it doesnt matter what DNS does under the hood.



In my opinion referencing a CNAME in that passage only serves to
confuse, as DNS itself is pretty much irrelevent. I would suggest the
"using a DNS CNAME record." should be dropped, as there are other
alias methods.  Pamela?



On 02/04/2009, rodivi <[email protected]> wrote:
>
>  Hi all!
>
>  I signed up for a map api key for domain http://www.publico.es/ but
>  I'm having some troubles with key validation.
>
>  We use a CDN (Akamai) to serve our pages, using a CNAME record in our
>  DNS servers, and I noticed at FAQ that it is not compatible with using
>  GMaps API:
>
>  "Note that a key for http://www.mygooglemapssite.com/ will only be
>  accepted when the site is accessed using this address. It will not be
>  accepted if the site is accessed by IP address (eg. http://10.1.2.3/)
>  or by a hostname that is aliased to www.mygooglemapssite.com using a
>  DNS CNAME record."
>
>  Is there some option to resolve this? I think mayor web sites that
>  uses CDN services and GMaps API are really common. So, how can they do
>  it?
>
>  Thank you all!
>
>  Rodrigo Díez Villamuera
>
>  >
>


-- 
Barry

- www.nearby.org.uk - www.geograph.org.uk -

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to