This is probably a dumb question but does www.google-analytics.com have a fixed IP? I ask because due to the vagaries of the project I'm on we need to make sure that traffic aimed at www.google-analytics.com (i.e. traffic from our website) does not get blocked at a certain point in the network. We can ensure it is not blocked with a rule, but the rule demands both a URL and IP address.
So do you know, is the IP address for Google Analytics fixed?
Cheers!
Dave
Related
could you please help me understand why am I getting Phoenix IP address when I ping my service? This site is fully behind Cloudflare CDN so I would expect it will serve me nearest datacenter which is Prague, Europe. Not Phoenix.
Ip I´m getting http://www.ip2location.com/104.31.80.242
thank you
This is an anycast address from CloudFlare, you can see it as CDN in the usage type in IP2Location. The exact server location depends to your own location. You could not use a geolocation database to detect the server location because there are many servers sharing the same IP address.
You can try to ping the IP address. If it is less than 50ms latency, then it should be very good.
G'day,
I have a client who wants to setup cross-domain tracking, but when you click through to their payment gateway you are redirected to an IP address rather than a domain name URL. I was able to find the DNS for some by using tracert on the IP address, but some of them are hosted on port 81 instead of port 80 and the URL only works if the port is specified.
Is there any way I can set up cross-domain tracking for these URLs? Will the auto linker param and referral exclusion user interface accept port 81? I cannot find this info on Google Analytics developer guides.
If anyone knows where I might look I would really appreciate it.
Thank you very much
Petra
We would like to use the Google Translate API from a host which doesn't have open access to the Internet. To setup the firewall rules I would need the list of possible IP addresses for www.googleapis.com. It is resolved to different IP addresses depending on the location. It seems to be difficult to create a future proof firewall rule.
Do you know how could I get the list of IP addresses or network ranges for the Google API servers?
The IP addresses used for any given googleapis.com server could change. Google doesn't have just one network block which they host all of their content out of, they have a bunch of them - and they change over time.
There are several ways you could setup your restricted network to allow access to *.googleapis.com without hard-coding IP addresses. I don't know anything about your setup, but I've found that using an internal proxy is often the best bet when you want to allow/restrict access to a domain.
A: represents my companies network IP address range (10.90.10.0-255) INTERNAL IP addresses
B: represents the larger organization that provides our network services (Not our ISP however)
C: Represents our website that has google analytics installed.
When I access the site will google analytics record the 10.90... IP address? Or will it only know of the external IP address that B pipes all traffic out thru? 234.255.255.000?
I really may not understand some basic concepts, but according to google this is possible.
https://www.google.com/support/googleanalytics/bin/answer.py?answer=55481&hl=en_US&utm_id=ad
But I agree with this forum. If it is not routable google will never know about it.
http://www.google.com/support/forum/p/Google%20Analytics/thread?tid=79087fbe4c6ade7b&hl=en
I would be inclined to believe that Google Analytics tracks the IP address that makes a request to Google's servers; thus, they would only see the external IP.
I have a requirement that I believe may be impossible and wanted to confirm this with experts in this community.
A client wants us to configure a DNS server to point all non-whitelisted domains to an IP address of a server on the internet. This server should forward / redirect all non-http traffic to an IP address associated with the real DNS record as accurately as possible. However, for all port 80 traffic, it should intercept the traffic and forward to a web proxy. This could in theory be possible if we had a large block of public IP addresses that could intelligently route based on the sender's IP to the proper destination, but the engineering effort required there to keep the DNS request and subsequent requests to that same domain in sync would be immense. Not to mention we would be limited from a concurrency perspective.This is probably similar to how OpenDNS does their DNS+Proxying, but they only seem to do it for google.com. This needs to work for an arbitrary set of domains (potentially all of them).
Is the above approach feasible? If not, are there other ways this problem can be approached short of requiring specialized gateway hardware?
Ideally the system will minimize bandwidth usage & latency for non-http traffic without requiring anything besides DNS or firewall configuration. I realize we can forward all http traffic at the firewall level, but the client wants to avoid http requests to CDNs or media heavy sites as well as minimize deployment effort across disparate network configurations.
OpenDNS works by blacklisting instead of whitelisting
When a host is blacklisted, openDNS will resolve the name into their IP address, which in turn prevent the client from accessing the real IP.
In your case, looks like you need transparent proxy where you can route all HTTP traffic to your proxy server:
See :
http://www.howtoforge.com/dansguardian-content-filtering-with-transparent-proxy-on-ubuntu-9.10-karmic
This might not be exactly what you are looking for but take a look at my article "How To Setup A Transparent Content Filtering Proxy" in which I utilize OpenDNS's blacklisting capabilities.
You can do it using two pieces:
DNS resolver configured with *. pointing to IP A.B.C.D (wildcard)
NGINX reverse proxy listening on A.B.C.D that proxy request to the domain present in the Host header.