: Configuring Google Domains/Domain Forwardings A complete webmaster noob here, and I'm sorry for the noobish question. I recently purchased a domain through Google Domains. I've also setup a personal
A complete webmaster noob here, and I'm sorry for the noobish question. I recently purchased a domain through Google Domains. I've also setup a personal Apache web server running off a non-standard port (ISP blocks 80), currently serving a default template wordpress site.
It is currently setup:
IP.ADDRESS:PORT
12.13.14.15:1111
Yields my site, on or off the local network. However, I would like to be able to simply type "www.mydomain.com" and have it yield the same page. I bought my domain through Google Domains and I have no clue on how to set this up.
I've tried working the problem out by applying the rules as seen in this link, under the SRV subheading.
_http._tcp SRV 1h 10 5 PORT(ex. 1111) mydomain.com.
www A 1h SERVER_IPADDRESS
How I understand the first rule:
Service http, protocol tcp, type SRV, 1h timeout, priority, weight, the port on my machine the request should be funneled through, and the domain
How I understand the second rule:
subdomain, type A, 1h timeout, my servers ip address
And so in my mind, I image these rules working like this:
Browser makes request for "www.mydomain.com"
Google Nameserver applies those rules,
My system recieves the request on port 1111, forwards that to port 80 of the server, and then feeds the browser the requested page
Applying these rules does not work (It tries to log me into my router instead of serving the landing page). Can anyone help me figure this out?
Side note: This isn't a website for others, just me learning and playing around. I know it's insecure, and I don't plan on having it up except for my playing around. I'm not very experienced so I don't know the ways in which it is vulnerable, however. If someone could tell/link me the risks of this setup, I'd love to learn.
Thanks!
More posts by @Karen161
1 Comments
Sorted by latest first Latest Oldest Best
SRV records are not designed to work with HTTP. No browsers support them.
From Why do browsers not use SRV records? by Teddy:
The RFC for SRV records specifies that it may not be used by pre-existing protocols which did not already specify the use of SRV records in their specifications. I.e. no SRV in the HTTP spec - browsers are, by the SRV standard, prohibited from using it.
This does not prohibit a new HTTP 1.2 standard from specifying the use of SRV records, though. However, Mark Andrews proposed this in April 2007 to the IETF HTTP working group, but got no response.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.