Apache virtualhost

Pozdravljeni

Že v naprej se opravičujem za odprtje nove teme z to tematiko,
ker sem prebral vse teme in forume v zvezi z mojo težavo in ni pomagalo nič se obračam na vas in upam da mi boste znali pomagati.

Imam win xp, apache 2.2.22, en ip naslov, in več domen

1. v datoteki httpd.conf imam vključeno
Include conf/extra/httpd-vhosts.conf


2. v datoteki httpd-vhosts.conf je sledeče

(Naslov domen je izmišljen, jaz imam napisane prave)

NameVirtualHost *:80

[VirtualHost *:80>
ServerName www.domena.com
DocumentRoot "D:/Server/"
ServerAdmin domena@siol.net
ErrorLog "logs/domena-error_log"
CustomLog "logs/domena-access_log" common
[/VirtualHost>

[VirtualHost *:80>
ServerName www.drugadomena.si
DocumentRoot "D:/Server/web_www/drugadomena.si"
ServerAdmin info@drugadomena.si
ErrorLog "logs/drugadomena-error_log"
CustomLog "logs/drugadomena-access_log" common
[/VirtualHost>

[VirtualHost *:80>
ServerName www.tretjadomena.si
DocumentRoot "D:/Server/web_www/tretjadomena.si"
ServerAdmin info@tretjadomena.si
ErrorLog "logs/tretjadomena-error_log"
CustomLog "logs/tretjadomena-access_log" common
[/VirtualHost>

ITD ITD

predznak < sem moral zamenjati z [ ker javi napako pri oddaji teme

3. probal sem že vse, tudi * sem zamenjal za ip naslov pa ne dela. vse kaj sem zasledil na forumih sem probal pa nič

ko vpišem www.domena.com ali www.drugadomena.si ali www.tretjadomena.si ITD
vedno mi pokaže prvo stran www.domena.com
Aja pa še to vse domene kažejo na moj IP naslov od strežnika

Prosim za pomoč
Hvala

vedno resetiral, -s ne pravi nič narobe

Poženi httpd -D DUMP_VHOSTS, da dobiš idejo, kaj si apache predstavlja, da si mu povedal v conf fajilh. Če si predstavlja isto, kar si mu hotel dopovedat, potem veselo s telnetom napadi port 80 in preveri, če stvar res deluje. Če deluje, vprašaj tvoj DNS, kam te pošlje, ko greš na neko od teh domen.

pegasus

evo prilagam sliko

NAT loopback

NAT loopback[edit]

NAT loopback, also known as NAT hairpinning or NAT reflection,[5] is a feature in many consumer routers[6] which allows a user to connect to his/her own public IP address from inside the LAN network. This is especially useful when a website (with domain) is hosted at that IP address. Consider the following network:
Public address: 203.0.113.1 (this is the address of the WAN interface on the router)
Internal address of router: 192.168.1.1
Address of the server: 192.168.1.2
Address of a computer: 192.168.100.1
When a packet is sent to 203.0.113.1 (public address) by 192.168.100.1 (a computer), the packet would normally be sent to the default gateway (the router). An exception could be made in the computer's routing tables, but by default the default gateway will be used. A router with the NAT-loopback feature will detect that 203.0.113.1 is the address of its WAN interface, and treat the packet as if coming from that interface. It decides based on DNAT (port forwarding) rules where the packet should go. For example, if the data were sent to port 80 and there is a DNAT rule for port 80 to go to 192.168.1.2, then it will send the packet there.
If no applicable DNAT rules are available, the router's firewall will drop the packet. An ICMP Destination Unreachable reply may or may not be sent. Note that if any DNAT rules were found, address translation is still in effect; the router still rewrites the source IP address in the packet. The computer (192.168.100.1) will send the packet as coming from 192.168.100.1, but just like when a packet was sent to any global IP address, the server (192.168.1.2) will receive it as coming from 203.0.113.1. When a reply is made by the server, the same thing happens again. The packet goes to the server's default gateway (the router), which will find the source and destination port in its NAT tables, and know that it originated from 192.168.100.1. This way, two-way communication is possible between hosts inside the LAN network via their public IP address.
NAT loopback is especially useful when a domain is hosted on the server. The domain name will resolve, unless the user is running a custom DNS server and has made an exception, to the public address. When the router does not have NAT loopback, any connection attempts to that IP address are discarded and time out. A workaround is to include the domain name in the hosts file,[7] but all subdomains would have to be included as well, and all devices in the LAN network would need to have the same modifications. Example entries for the hosts file, following the above network setup:
192.168.1.2 example.com
192.168.1.2 subdomain.example.com

google ti ne gre a ne?

ce ves kaj je nat, potem ves, kje moras to narediti?

to ni za tebe!
poleg tega, da si len(miljon linkov na to temo), in da pricakujes, da bodo drugi naredili namesto tebe

prvo pricakujem od tebe, da se ne javis tukaj kaksen teden
v tem casu pa beri, pa googlaj

pac samo videti je, da cakas, nic ne preberes
ko bos, ce bos, prebral navedel kaksen link, kjer si prebral, in povedal kaj te muci, bos vedno dobil pomoc

se pa postavi na drugo stran, da ti pomagas nekomu, in da ti taksen post napise, da se osnove ne pogleda, kako mu bos pomagal?

bos priznal, da je najboljsa pomoc, da ga skurcas, ker je len, in da naj prvo pogleda, in se pol vrne

posteno?