Creating DNS entry for website

Are you going to make this available on the web or just on browsers on your LAN?

Hi there

Just browsers on our internal network for now.

You can use a DNS alias to resolve APP1 to SERVER1.MYDOMAIN.COM/etc

Yes, just make a manual entry in your DNS zone that pointst the IP address of the host to the DNS name. Teh you should be able to type it in a browser to access it.

Thanks guys

Ok, let's say the IP of server1 is 192.168.1.10

Are you saying that I need to add an entry that points

192.168.1.10 > app1?

Or an Alias that points

app1 > server1.mydomain.com/application1/web

Or both?

@kam_uk:

Justin_W_Chandler's answer is incorrect.

wantabe2's last comment was partially accurate, just incomplete.

What you specifically are asking for cannot be done ONLY with DNS.  DNS is a technology to translate FQDN to IP, IP to FQDN, and identify the FQDN of domain service records.  

What you want is an A or CNAME that directs to server1.mydomain.com.  DNS can be used to create your "app1" alias, and that will get you to the web server "server1.domain.com".  From there, you need to use a webpage redirect on the server1 web server to specifically reference the page "server1.mydomain.com/application1/web".  DNS can get you to the correct web server, the web server itself will have to tell the user what directories/pages to access.  A simple redirect is the answer.

I answered a previous question that is somewhat similar to what you are looking for.  A little more history on that can be found here:

https://www.experts-exchange.com/questions/23881034/Please-make-this-simple-CNAME-DNS.html

Hope this helps, post back if not!! :)

I'm not sure how you could necessarily say that my answer is incorrect, when you say "DNS can be used to create your "app1" alias, and that will get you to the web server "server1.domain.com".", which indicates that I am, in fact, correct. As far as directing to the exact page, of course that's handled by the web server operating on SERVER1.MYDOMAIN.COM. In this case, it could be sent to app1.MYDOMAIN.COM, which would be interpreted by the web sever as a specific page on it's host list. While I'll grant that your answer includes some more information; my answer was definitely not incorrect.

Justin-I apologize if you thought my comment was offensive, it wasn't meant to be.  I wanted my response to be crystal clear to the author.  It is clear from your last comment that you understand how it works.  But your first comment indicated that a DNS alias could be used to resolve ".../etc" and that would be very confusing to the author because DNS cannot do that on its own.  Best regards!

I thought I would throw a small comment out there on this topic....

The host name "app1" is not a FQDN and therefore would not use DNS resolution unless the client is configured to append the proper DNS suffix. The name resolution process is different for "app1" vs. "app1.company.com"

In most cases, that is not a problem...especially if part of a domain....but something to keep in mind.

BRWWIGGINS good point. MYDOMAIN.COM should be appended by default as long as the client computer being used is also part of that domain.

RVTHOST yes, I see where you're point comes from. In fact, I recognized that fat finger (should have been a comma) but was not allowed to edit the post.

give the points to Justin

/TT

Ok - am a little confused.. :(

Ok, let's say the IP of server1 is 192.168.1.10

Currently, the application can be accessed via

http://server1.mydomain.com/application1/web

I wish for the application to be accessed at

http://app1.mydomain.com 

What do I need to do?

[sorry]

Thanks all - much appreciated...assigning points equally between Justin and Rtvhost, but thanks to all!