I run linux slackware ver 2.2.19 I have a registerd domain.. my question is this.. can i setup the DNS to resolve a name to my internal (non public ip's) ? Lets say www.mydomain.com goes to the aapche server on the slackware box (public ip) but I want games.mydomain.com to resolve to my Win 98 box (non public ip) ? I have seen a few help files on this but there shotty at best.. Thanks in advance

NO, people on internet cannot reach an non-public IP directly. They must access a Public IP address, and you must redirect this specific tcp port to a local IP (LAN) address. Portmapping may be done with several router of Nating softwares.

Thanks.. but I am port mapping.. Here is a nother example.. My apache server can do virtual host and point alias request to other containers and Ip's.. my DNS can do the same thing.. how do I resolve a name request to a port mapped internal Ip.. I know there must be way becouse I am shure ISP's have several boxes that are non public. I think it has somthing to do with the pc name.. and then asighn DNS Cnames.. Any idea would be great.. thanks

Don't mix up things! Virtual hosts are done by apache server, either IP-based or name-based. The HTTP/1.1 protocol contains a method for the server to identify what name it is being addressed as. The most browsers can use HTTP/1.1, but there are a lot of older ones, which could not access those name-based virtual hosts. And you need all the people who have their web sites hosted on this apache server having their DNS (www.domain.com) point to the same IP ! If the ISP who is hosting those web sites also runs their DNS, everything is OK. If you use Name based virtual hosts, you can't use the 'main server'. That means, a query for http://xxx.xxx.xxx.xxx will fail. What you are looking for is port forwarding, NOT port mapping. It is possible, you have to use asquerading, pointing certain ports to an internal private address, read http://www.ox.compsoc.org.uk/~steve/portforwarding.html http://www.ox.compsoc.org.uk/~steve/portfw-2.2.html by Steven Clarke

DNS entries are ALWAYS pointing to a public address. name resolved by dns server have nothing to do with ports you need to reach. When a request will be sent to the public ip address, this host/router may forward to somewhere else on the LAN, but this is transparent to the remote users and dns severs. The term "virtual hosting" doesnt refer to a non-public address at all. I repeat again... if a dns server by error resolve a LAN ip such as 192.168.0.2, remote user will NEVER be able to reach it since there is no route for that!!!

Respected sir, I have installed linux and apache server of my server.. also entered my all site data to wwwroot... but i dont know how to access it through telnet support.. can you please inform me so i can do it... thanking u. hoping early reply from you.