• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DNS Newbie Question

SaltBoy

Diamond Member
I was wondering that if I were to set up a DNS name, could it point to the port of an IP address.

Port 80 is the default, but I want DNS to go to port 8150. For example, I want www.mydomain.com to point to 128.64.32.16:8150 and NOT 128.64.32.16:80.

Is this possible?
 
Originally posted by: SaltBoy
I was wondering that if I were to set up a DNS name, could it point to the port of an IP address.

Port 80 is the default, but I want DNS to go to port 8150. For example, I want www.mydomain.com to point to 128.64.32.16:8150 and NOT 128.64.32.16:80.

Is this possible?

No. DNS does not resolve ports.
Bill
 
Originally posted by: bsobel
Originally posted by: SaltBoy
I was wondering that if I were to set up a DNS name, could it point to the port of an IP address.

Port 80 is the default, but I want DNS to go to port 8150. For example, I want www.mydomain.com to point to 128.64.32.16:8150 and NOT 128.64.32.16:80.

Is this possible?

No. DNS does not resolve ports.
Bill
Okay, so when the DNS resolves to the IP address, the web server (using IIS, or whatever) that has the IP address will need to be configured to default to a specific port if that's where I want it to go. Right?
 
Okay, so when the DNS resolves to the IP address, the web server (using IIS, or whatever) that has the IP address will need to be configured to default to a specific port if that's where I want it to go. Right?

Correct. As you already posted, the default port for HTTP is 80, so if you configure IIS with a web on 80 it will be what is found if a user enters your url without the :8150 part (based on your example).

Bill
 
here is how it works:
you type https, it goes to 443
you type ftp, it goes to 21
you type http, it goes to 80
you type http://blah blah.net:8150, it goes to 8150
if you want to hit a specific port, you need to include it in the url.
this is the only way it will work, if port 80 is blocked. Of course, it is likely blocked for a reason, probably something having to do with Terms Of Service with your ISP.
 
Back
Top