sirvodka
asked on
DNS pointer for internal website
I have an internal server hosting a helpdesk application website that I access from IE with http://server:9545/helpdesk.
I would like users who enter helpdesk tickets to be able to enter http://help in IE to access the application. (I know they can just create a favorite)
I assume this can be done through some type of pointer/forwarder in DNS but I am unable to get it configured correctly. Any help would be greatly appreciated. Thanks.
I would like users who enter helpdesk tickets to be able to enter http://help in IE to access the application. (I know they can just create a favorite)
I assume this can be done through some type of pointer/forwarder in DNS but I am unable to get it configured correctly. Any help would be greatly appreciated. Thanks.
you need to create an alias record (CNAME) in your forward lookup zone that is called by your domain name. In MS DNS right-click the zone and click new alias.
If the server is on an internal network with private addresses you also need to set up a forwarding rule in your firewall to enable external users to reach the server.
The CNAME mentioned by fetch needs to point to a public IP address which the forwarding rule then will translate to the private address (sounds more complicated than it is)
ASKER
Thanks for the responses.
External users do not need to access the helpdesk server.
I have attempted the Alias (CName) record several times with no success. I must not be configuring it correctly. Could you give me an example?
Thanks.
Steve
External users do not need to access the helpdesk server.
I have attempted the Alias (CName) record several times with no success. I must not be configuring it correctly. Could you give me an example?
Thanks.
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oh, I noticed one thing in your question-- http://server:9545/helpdesk is how you get to it, but to make it redirect to http://help you also need to change the default website and listening port for that server. Those are in IIS (assuming again you're using MS.) My IIS skills are lacking,so I'll let someone else tell you the best way to set that up.
But do try and ping help. If you get a response, you know the DNS is correct and it's a website issue.
But do try and ping help. If you get a response, you know the DNS is correct and it's a website issue.
ASKER
fetch,
I am now able to ping and get a response with "help".
Looks like the listening port for the website will have to be changed to 80 to allow http://help to work. Right now I can get to it with http://help:9545
We're getting close.
Steve
I am now able to ping and get a response with "help".
Looks like the listening port for the website will have to be changed to 80 to allow http://help to work. Right now I can get to it with http://help:9545
We're getting close.
Steve
yes, the default port for http (hypertext transfer protocol) is 80. Your browser assumes 80 unless you tell it otherwise with the :9545 part of the URL.
In IIS, if you rt-click your website that hosts the help page, you can go to properties and change the TCP port to 80. Make sure you don't have another website using 80, or you'll get an error and IIS won't take the change. I think that's all there is.
In IIS, if you rt-click your website that hosts the help page, you can go to properties and change the TCP port to 80. Make sure you don't have another website using 80, or you'll get an error and IIS won't take the change. I think that's all there is.
ASKER
fetch,
thanks for the help.
Steve
thanks for the help.
Steve
Glad you were able to get it working.