<div>
You can't define ports in DNS or Host name. If you're using a port other than 80 to communicate with an HTTP based website, you have to include the port at the end of the FQDN like this: <a href="http://myappservice.com:6000/remainingurl" rel="ugc">http://myappservice.com:6000/remainingurl</a><br />
<br />
There really isn't a way around this without using a firewall to translate one port to another (which you could possibly do with Windows Firewall).
</div>


You can't define ports in DNS or Host name. If you're using a port other than 80 to communicate with an HTTP based website, you have to include the port at the end of the FQDN like this: http://myappservice.com:6000/remainingurl [http://myappservice.com:6000/remainingurl]

There really isn't a way around this without using a firewall to translate one port to another (which you could possibly do with Windows Firewall).

<div>
Create a CNAME in DNS and change port to 80 (preferably 443 with a certificate)<br />
If you already have website on 80/443, use host headers to route to correct site
</div>


Create a CNAME in DNS and change port to 80 (preferably 443 with a certificate)
If you already have website on 80/443, use host headers to route to correct site

<div>
<div class="content wysiwyg-content">
Hello all,<br />
<br />
I have a wep api setup as a windows service running against a port like 6000. &nbsp; How can I set a host name up like <a href="http://myappservice" rel="ugc">http://myappservice</a>.... instead of the computer name and port to reach it?
</div>
</div>


Hello all,

I have a wep api setup as a windows service running against a port like 6000.   How can I set a host name up like http://myappservice.... instead of the computer name and port to reach it?

Setting up host name on windows service port.

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.