Hi all,
I use a NETGEAR DG834G Wireless ADSL Router to automatically update cherif.dyndns.org with my new IP.
But it doesn't work, because I tried to reach cherif.dyndns.org with a browser outside of my home without success.
When I use checkip.dyndns.org to find out my IP, I get 213.140.57.x, but when I checked my account at dyndns.org, I see 10.10.x.x wich is a private IP address.
Finally I read the doc about Dynamic DNS an it says that if my ISP assigns a private WAN IP address such as 192.168.x.x or 10.x.x.x, the Dynamic DNS service will not work because private IP addresses will not be routed on the Internet.
So my question is what is my IP address on the internet, and how could I solve the problem knowing that I am using NAT ???
Thanks for your answers...

Did you attempt to reset your IP while on the DynDNS.com website (using their update page), then try hitting "cherif.dyndns.org" again? I believe only certain routers are "approved" by DynDNS for doing updates, don't know offhand if yours is or not?

Hello again,
Now I'm using "ddclient" to update my IP every minute from "checkip.dyndns.org", also I configured my router to forward incoming requests to IP 192.168.0.2 port 80 and "apache" to listen to IP 192.168.0.2 port 80.
But "cherif.dyndns.org" still doesn't work from outside, why?
Also using my current public IP from outside gives nothing either!
Has NAT something to do here?
Please help me, I'm really puzzled!!!

This time I added a second NIC wich has IP "192.168.0.3" dynamically assigned by the router, and allowed any TCP port to be reached by outside clients.
I also configured "apache" to listen to IP "192.168.0.3".
But when I try "cherif.dyndns.org" from outside with IE (I have no other choice);
I get "Socket Error, connection to Remote Host timed out".
Also I have this reported by my router's log:
"TCP Packet - Source:10.10.0.149,11498 Destination:192.168.0.3,139 - [Any(TCP) match]"
"TCP Packet - Source:10.10.35.232,1729 Destination:192.168.0.3,445 - [Any(TCP) match]"
And so on...
What does it mean?
Could somebody please try to reach "cherif.dyndns.org" with firefox and tell me what he gets?!

It looks like cherif.dyndns.org IS set up properly at DynDNS - when I do a ping on that url I see your IP as 81.52.161.79. Unfortunately, neither your domain name nor your IP seems to be responding. Is it possible your ISP is blocking any outside requests? Finally, are you able to see your website by opening a browser on your machine and trying "http://localhost"? I don't see in your previous posts if you've tried that or not, but at least if you CAN see your site on the server itself, you'll know your webserver's running properly.

Thanks a lot pnellsen for trying to help me...
In my "listen.conf" file I changed "Listen 192.168.03:80" to "Listen 80" and now I can try "http://localhost" successfully. But does it solve my problem ?
Also I wonder why I get an error with "Listen 81.52.161.79:80" ?
I remember that when I had an RFC 1483 bridge connection, I could bind to that specific address with "apache", but now I am using PPPoE protocol !!!

When you specify an IP in the Listen statement, you must use the IP of a local network interface. For example, if you want to listen on eth0, and eth0's IP is set to 192.168.0.3, you can use "Listen 192.168.0.3:80". Be aware that you should statically assign IPs to your server, or configure the DHCP server to always give you the same address based on MAC (can only be done with some routers). However, most broadband ISPs block port 80 on residential packages. Try changing the port you listen on to something else, like 81, 82, or 8080, and testing by going to "cherif.dyndns.org:81" (or whatever port you chose).

I allowed TCP ports from 1 to 65535 in the router's config, but still cannot access the web server from outside !!!
Also, I am using the LimeWire file sharing program, and other users are able to download files from my computer to their's using port 49951 !!!
So I wonder why isn't it working for HTTP requests ???

Maybe you need to set up iptables for unblocking traffic flow on your server:
try this
iptables -A INPUT -p tcp - d 192.168.0.2 --dport 22 -j ACCEPT
iptables -A output -p tcp -m STATE --state RELATED, ESTABLISHED --s port 22 -j ACCEPT
also check firewall settings on server

and if you can help me, my situation is similar but ip address is working correctly from outside internet for me but the name address not! I need set up DNS? My server locally runs DNS and local network addresses could resolve. So maybe another configuration is needed.

PS> this infomation could be little bit outdated for you...

Hi all :
In algeria ISPs are assigning private IP's (10.x.x.x) and these, of course, aren't seen from the internet. LIKE most ISP worldwide, and if you ask for STATIC PUBLIC addreess (if you're ready to pay for)... they'll say: what are you talking about?!!! . Glory to those funny days (1999-2002) with cerist.dz which was assignig public IPs and we were able to share what we like with people worldwide using free DNS....
Anyway, we should look around to break this wall.
++++++
Knowledge is POWER.