***FOR INTERNAL USE ONLY***
End users reach nature.com through Akamai servers. To them, it looks like nature.com but they are actually accessing Akamai servers.
We use Akamai because it’s the fastest way for users to get to nature.com. There are 20,000 AKamai servers around the world. When an end user tries to access nature.com, it does so by going through the closest Akamai server.
While Nature.com IP addresses are stable, Akamai’s are dynamic. They change every second. You can see this by doing a DNS lookup. That’s why we aren’t able to give a list of our IP addresses to customers. It’s not because we don’t want to.
VPN- a way of remote access. User sees nature.com as they normally would in their office. URL would look like www.nature.com
Proxy- most of the time, there’s a long prefix to www.nature.com. It’s a way for a user to stay within their university’s website while browsing our site.
If they have a strong firewall, it might prevent them from accessing nature.com. To allow nature.com, they shouldn’t allow it via IP addresses (because Akamai’s IPs change all the time) but by name ie “nature.com”. If they don’t want to allow access by name, a workaround can be using a DNS lookup to see which servers they hit and putting in a range of IPs on their system. However, as soon as Akamai’s IPs changes, they would lose access. This IP change could be in 6 months or 6 days.
External IP- what the world sees. What the internet sees. What customer must give us for access ie 220.127.116.11. This is what debug sees.
Internal IP- or private IP ie 172.26.7.4. Customers should not be giving us their internal IPs. Their IT dept should be able to tell us their external IPs.