mesican
asked on
NAT and DNS
I have my cisco router doing nat for my only public ip address, a.b.c.d. I have my zone file set on my dns server to point my web, mail, and dns to my public ip a.b.c.d.
My question is this. I want people that type in webmail.example.com to go to the mail servers web page and the people who type in www.example.com to go to the www server. But I only have 1 ip and the both use port 80. So i made the router use 8080 for webmail but i dont know how to set that in dns.
DO you?
My question is this. I want people that type in webmail.example.com to go to the mail servers web page and the people who type in www.example.com to go to the www server. But I only have 1 ip and the both use port 80. So i made the router use 8080 for webmail but i dont know how to set that in dns.
DO you?
Have you thought of using the DNS headers to separate the two sites? They can both sit on the same IP address but if the DNS headers are different then the traffic gets forwarded to the relevant page.
ASKER
How would you use ths dns header to seperate the two sites?
Would I need to buy another piece of hardware?
Would I need to buy another piece of hardware?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> i made the router use 8080 for webmail but i dont know how to set that in dns.
The answer is you can't
but you can redirect, I gave him one way to solve his problem, interax gave him another, and you gave him a third...
mesican, please come back and tell us what you finally implement
The answer is you can't
but you can redirect, I gave him one way to solve his problem, interax gave him another, and you gave him a third...
mesican, please come back and tell us what you finally implement
>The answer is you can't
Apparently someone begs to differ.
>interax gave him another
I'm utterly unconvinced of that, and your solution was not what he wanted, which was to have two distinct domains (or subdomains) which transparently serve up different content from one another. My answer was the only one with that distictive "Yes you can" that answered the original question. Allow me to refresh your memory:
>My question is this. I want people that type in webmail.example.com to go to the mail servers web page and the people
>who type in www.example.com to go to the www server
He didn't say it couldn't redirect ,*you* did. My answer gives him exactly the functionality required in the original question. 'Nuff said.
Cheers,
-Jon
Apparently someone begs to differ.
>interax gave him another
I'm utterly unconvinced of that, and your solution was not what he wanted, which was to have two distinct domains (or subdomains) which transparently serve up different content from one another. My answer was the only one with that distictive "Yes you can" that answered the original question. Allow me to refresh your memory:
>My question is this. I want people that type in webmail.example.com to go to the mail servers web page and the people
>who type in www.example.com to go to the www server
He didn't say it couldn't redirect ,*you* did. My answer gives him exactly the functionality required in the original question. 'Nuff said.
Cheers,
-Jon
not one to want the last word ....
Mexicano,
díganos qué sucede
Mexicano,
díganos qué sucede
You can use your webserver at port 80 to redirect though.
If you publish www.example.com and www.example.com/mail, you can put a page at /mail that redirects them to www.example.com:8080 which will port forward to your other server.