[Android Apps and Games] ipdev:
Special ip address are designated by the [I can not think of the organizations that handle all the ip/domain stuff.].

127.0.0.0 to 127.0.0.8 are Loopback.

0.0.0.0 to 0.0.0.8 are "This network".

Normally you would use 0.0.0.0 with multiple ip address.

With a server set to "This network", connected to multiple networks (server is connected to multiple network address), it will listen across all the networks it is attached to.

Each network would be able to connect to the server.​

In this case, it would not make a difference.

The redirect will still be handled by localhost.

So the response will still come back from 127.0.0.1 even if you call 0.0.0.0.

Example:

flo:/ # cat /system/etc/hosts | grep 'amazon-'
0.0.0.0 aan.amazon-adsystem.com
0.0.0.0 aax-eu-retail-direct.amazon-adsystem.com
0.0.0.0 aax-eu.amazon-adsystem.com
0.0.0.0 aax-fe-sin.amazon-adsystem.com
0.0.0.0 aax-fe.amazon-adsystem.com
0.0.0.0 aax-us-east-rtb.amazon-adsystem.com
0.0.0.0 aax-us-east.amazon-adsystem.com
0.0.0.0 aax-us.amazon-adsystem.com
0.0.0.0 aax.amazon-adsystem.com
0.0.0.0 amazon-adsystem.com
0.0.0.0 amazon-tam-match.dotomi.com
0.0.0.0 c.amazon-adsystem.com
0.0.0.0 cdn-a.amazon-adsystem.com
0.0.0.0 fls-eu.amazon-adsystem.com
0.0.0.0 fls-fe.amazon-adsystem.com
0.0.0.0 fls-na.amazon-adsystem.com
0.0.0.0 ir-de.amazon-adsystem.com
0.0.0.0 ir-na.amazon-adsystem.com
0.0.0.0 ir-uk.amazon-adsystem.com
0.0.0.0 mads.amazon-adsystem.com
0.0.0.0 ps-eu.amazon-adsystem.com
0.0.0.0 ps-us.amazon-adsystem.com
0.0.0.0 rcm-eu.amazon-adsystem.com
0.0.0.0 rcm-na.amazon-adsystem.com
0.0.0.0 s.amazon-adsystem.com
0.0.0.0 vaes.amazon-adsystem.com
0.0.0.0 wms-eu.amazon-adsystem.com
0.0.0.0 wms-na.amazon-adsystem.com
0.0.0.0 ws-eu.amazon-adsystem.com
0.0.0.0 ws-na.amazon-adsystem.com
0.0.0.0 z-eu.amazon-adsystem.com
0.0.0.0 z-na.amazon-adsystem.com
flo:/ #
flo:/ # ping -c 5 amazon-adsystem.com
PING amazon-adsystem.com (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.122 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.183 ms
64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.122 ms
64 bytes from localhost (127.0.0.1): icmp_seq=5 ttl=64 time=0.152 ms

--- amazon-adsystem.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 0.122/0.158/0.214/0.038 ms
flo:/ #
flo:/ # ping -c 5 0.0.0.0
PING 0.0.0.0 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.183 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.244 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.214 ms

--- 0.0.0.0 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.122/0.195/0.244/0.043 ms
flo:/ #
flo:/ # ping -c 5 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.122 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.153 ms

--- 127.0.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.122/0.146/0.214/0.038 ms
flo:/ #

Make sure to scroll down though the example to see the ping results.

Hope it helps more than confuse. 🙃

Cheers. :cowboy:

PS.

Quick search.

Internet Assigned Numbers Authority.

IPv4 Special-Purpose Address Registry - iana.org - Link

Note:

Good thing I checked. ;)

I was calling "This network" "Current network". 🙃