Tomcat does not supply DNS services. The client has to obtain them from a DNS server.
Most common web browsers will take a simple name like "abc" and expand it to "www.abc.com". DNS servers will sometimes contain extra information to assist in finding a default fully-qualified domain name when given a partial domain name. They also support alternate (alias) names for servers.
So for all of your examples, a properly configured authoritative DNS server will handle all of your URLs and Tomcat doesn' get involved.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jul 14, 2010
Thanks for replay.
But Most of application has using production on the tomcat server. Right?
DNS converts domain names to IP addresses, but it doesn't do ports. So unless a user provided an explicit port ID, their web browser would assume port 80 for http or port 443 for https.
To redirect internally to localhost:7070 - which normally is a WebLogic server (not Tomcat), you'd do something like use Apache HTTP server as a frontend. You can set up an ajp proxy rule in apache that will take URLs addressed to the Apache server on ports 80 and 443 and redirect them to localhost:8009, which is Tomcat's HTTP port.
Then again, if you're actually running WebLogic, Tomcat ajp proxying wouldn't work and you need to either go back to the WebLogic documentation or ask about it on our WebLogic forum.