NuclearVision wrote@rolf then how am i able to surf the web, doesn't it involve requesting page meaning i have my own ip.
Surfing the web involves you requesting a page from a server, not the opposite. The answer is matched to your private IP using NAT (Network Address Translation) masquerading.
The principle is like that. You have three persons: Toni, Kamal, and Ali (to preserve the confessional balance).
Toni wants to send a message to Ali but he can't. Kamal is the router. The message is "what did you eat today?"
Toni tells Kamal to ask Ali what he ate today. Kamal asks Ali "what did you eat today?". Ali answers "Tabbouleh". Kamal forwards the message "Tabbouleh" to Toni.
This is how Toni communicated with Ali. But if Ali wants to communicate with Toni, he can't, because he doesn't even know that Toni exists.
This is very basically what happens. If it doesn't make sense, then please look it up... NAT and private networks... I am tired and I learned it all by myself so maybe you can too.
Ah BTW, when you try that DNS thing, let me know what happens, I'm curious :)
But don't expect my help. I think I did enough.
UPDATE: I was able to get a redirect from no-ip.com which tracks my ip address which is good, but i am the only one who can access it.
Did you use your private IP for that (172.xxx)? Then yes you and anyone
on your local network will be the only ones to access your computer.
NuclearVision wroteWhen i type the address begining with 172. i am able to access my apache server. But if i do that on my phone using 3g, the webpage is not available.
Any ideas?
Yes, how about you listen to me? For example when I said:
it is impossible to contact a computer by using it's private IP without some kind of tunnel or port forwarding.
(that is Impossible to contact from the Internet)
For port forwarding, you need to contact your ISP and have them forward connections to 64.xxx port 80 to your private IP. I strongly doubt they will (or even can) do it.
For tunneling, I described a setup previously. There is also the option of an IPv6 tunnel. A while ago, some companies offered it for free, but I have very little info on that.
My advice is forget it, until you can get a public IP - and even then it's not guaranteed, some ISPs set up firewalls that will block it. I think Ogero DSL (for one) will give you a public IP, but I don't know if it's blocked by a firewall or not.
It needs to be a public IP. Not necessarily a dedicated IP. That's where dynamic DNS comes into play. If you have a public IP, but it's not dedicated (it's dynamic), then you can use the DNS thing.
But from the looks of it you don't even have a public IP.
According to wikipedia, these are the ranges of private IPs:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
These are used inside private networks (like yours apparently) and
not directly accessible from the Internet. But you can access the internet if you have a private IP, by using NAT. Using this method, several computers can share a public IP.
Why not? Because they're not unique. take the address 172.16.1.12 for example, there could be thousands of computers using this address accross the world. Anyone with a network can use it if he wants to. He doesn't need to register it with a public authority. It's a private address.
But a public IP is
unique accross the world. Public IPs are all registered and assigned with a central authority (
IANA).
How can you reach a computer which has a private IP if this IP is not unique accross the world? Can you call someone on his phone when 10 other persons have the exact same number?
That is why you need a "public IP".