cooperrd
asked on
How to point "A" record to a port
I have a situation that I need a sub domain or A record to point to a port. Example 10.0.0.1:5000. I want to be able to access that by using test.mydomain.com
I thought that I need to setup an SRV record – but I have not been able to make this work. Most of the domains that I need to do this on are hosted at Wildwest or enom.
Thanks for the help.
I thought that I need to setup an SRV record – but I have not been able to make this work. Most of the domains that I need to do this on are hosted at Wildwest or enom.
Thanks for the help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Since DNS records (A Records) only deal with name --> IP translation, the port depends on the details that DNS cannot control. If you provide more details to the requesting and servicing ends of this request we may be able to help.
An example SRV record in textual form that might be found in a zone file might be the following:
_sip._tcp.example.com. 86400 IN SRV 0 5 5060 sipserver.example.com.
You will also have to create an A Record to the resolve to the IP Address.
_sip._tcp.example.com. 86400 IN SRV 0 5 5060 sipserver.example.com.
You will also have to create an A Record to the resolve to the IP Address.
ASKER
Thank you all for responding.
Here are my settings - I am getting "page not found" - I have no problem connecting via ip address:port. Also I can ping the "a" records. I am trying to port to a file manager on a synology NAS
A Records:
http.test.mydomain.com
test.mydomain.com
SRV settings:
Service: _http
Protocol :_tcp
Name: test
Priority: 0
Weight: 5
Port: 5000
Target: test.mydomain.org
Here are my settings - I am getting "page not found" - I have no problem connecting via ip address:port. Also I can ping the "a" records. I am trying to port to a file manager on a synology NAS
A Records:
http.test.mydomain.com
test.mydomain.com
SRV settings:
Service: _http
Protocol :_tcp
Name: test
Priority: 0
Weight: 5
Port: 5000
Target: test.mydomain.org
In that case you must do one of two things...
Make URLS include http://serveripordns:5000 (actually have the port in the url)
or
use a tool that redirects port 80 to port 5000 (assuming you do not already have something running on port 80). If you need I can send you a tool I use to redirect ports.
Make URLS include http://serveripordns:5000 (actually have the port in the url)
or
use a tool that redirects port 80 to port 5000 (assuming you do not already have something running on port 80). If you need I can send you a tool I use to redirect ports.
ASKER
Well, I guess I will have to continue just using the port at the end of the url. I am using port 80. It just seems to me there should be away to do this. I have port redirects for a bunch of stuff. From rdp to media servers. My users have problems with urls much less ports. I realize I can create clickable links – but that is a pain.
Thanks everyone for the help.
Thanks everyone for the help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok so either this was a typo here or on godaddy:
A Records: --------- Both look good
http.test.mydomain.com
test.mydomain.com
SRV settings:
Service: _http
Protocol :_tcp
Name: test
Priority: 0
Weight: 5
Port: 5000
Target: test.mydomain.org ---- This should be http.test.mydomain.com
That's where I was talking about the duplicate stuff needed. With their DNS it has to be to that additional hostname that you created.
A Records: --------- Both look good
http.test.mydomain.com
test.mydomain.com
SRV settings:
Service: _http
Protocol :_tcp
Name: test
Priority: 0
Weight: 5
Port: 5000
Target: test.mydomain.org ---- This should be http.test.mydomain.com
That's where I was talking about the duplicate stuff needed. With their DNS it has to be to that additional hostname that you created.
ASKER
I just used a redirect