Subdomain pointing to Another Address

Hi,

So I own a domain example.com.

I subscribe to an email hosting plan and a website hosting plan from provider A. To access the webmail service, I would type https://srv115.ProviderA.com:2096 and to access the cpanel page, I would type https://srv13241.ProviderA.com:2083

To ease remembering, I setup 2 subdomains, details as such:
Name = webmail
Type = A
IP = 11.22.33.44

Name = cpanel
Type = A
IP = 66.77.88.99

With the webmail I can type webmail.example.com and it would be directed to https://srv115.ProviderA.com:2096. In fact the address at the browser remains webmail.example.com throughout login, sending email and such.

However, with cpanel I cannot access https://srv13241.ProviderA.com:2083 by typing cpanel.example.com

Accessing via IP addresses to both the webmail or cpanel result in error.

Thus my question is, why is the webmail configuration works yet the cpanel config doesn’t work? What can I do so that I can access to https://srv13241.providera.com:2083 by simply typing cpanel.example.com ?

Thank you
Henry

When you’re talking about DNS, there’s no concept of ports i.e. ‘:2083’. To redirect you in a browser, you can use a page rule. See here: https://support.cloudflare.com/hc/en-us/articles/218411427

If you want to hide the ‘providera.com’ URL to users, you can use a cname record but you’ll still need to append the port number like this:

webmail.example.comsrv13241.providera.com
cpanel.example.comsrv115.providea.com

To access in a browser, go to https://webmail.example.com:2096
To access the cpanel, https://cpanel.example.com:2083

Hi,

Thanks for the reply.

I have been reading everywhere and yeah, DNS does not support port. And that is what confusing me, why is it with webmail.example.com works, yet cpanel.example.com doesn’t.

I thought it might had to do with configuration at the server side, but even with webmail.example.com it does not deliver consistent result.

right now it works like this:
access via IP = error
access via webmail.example.com = works
access via srv13241.providera.com = error
access via srv13241.providera.com = works

whereas it should had been
access via IP = error
access via webmail.example.com = error
access via srv13241.providera.com = error
access via srv13241.providera.com = works

I did not create any page rule in CF.

bewildered.

If srv13241.providera.com works, it means that the webpage is also available on port 80 or 443 (https) so that’s simple.

The IP address not working is probably because that IP address is responsible for different services and is not supposed to be used directly i.e. it doesn’t know where to direct your traffic.

I think you made a typo in your reply because options 3 and 4 are the same. Can you correct that?

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.