I need some help, I can not find my answers, certainly because I am not asking my self the right questions. So here's the thing, in my very own home, in the very own room I'm writing this I got a dedicated machine running apache server. As well I bought the cheapest domain name I could find in order to make some experiments. But I can not seem to point my domain to my dedicated server. I don't understand how to do it. I suppose it important to say that my ISP uses dynamic IP addresses. Could someone point me toward some documentation please?
When you are talking about your very own home, than you are talking about sitting behind a NAT. Thats means, that your router/gateway has to forward Port 80 to your apache server.
Moreover, you have to use a dynamic DNS solution (dyn.org, no-ip.com, ...) to link a domain to your dynamic ip address.
However, it is not possible to link a generic domain to a dynamic ip address.
Related
I have recently acquired a domain name from GoDaddy. At home i am trying to setup a nextcloud server. Since my ISP serves me a dynamic IP addresse i had to create another domain name on no-ip website. Furthermore, i want to forward http requests to https. The following questions rises:
Do i create the ssl certificate (with let’s encrypt) for the godaddy domain or the no-ip domain?
What is the correct forwarding sequence here? Assume godaddy is foo.com and no-ip bar.dyndns.me and the user types foo.com, my server apache settings would forward foo.com:80 to :443 but this i guess should be corrected to my dyndns. I am confused.
I would appreciate any help - thank you.
you are making it too complicated. Instead of using a redirect you should request a static ip from you isp. this costs money varying by your provider but then you only need one domain. you then apply the ssl certificate to that domain and enforce ssl only with your hosting server (i.e apache, iis).
You can write a simple app/script to manage the Dynamic DNS from your server using the GoDaddy Api, thats what i have been doing for ~3 years now as my ISP want a stupid amount for a static IP. I have mine pinging out every 10 mins to check if my IP changed (ISP sucked for a while and mine would change several times a day)
Here are some links to various implementations of the GoDaddy API
BASH
Python
Powershell
So I think I have a fix for this, before I give you my answer I will outline problems with other solutions.
Static IP from your ISP. The problem with this is it may cost too much. (However if it’s cheap I’d probably do this solution)
Script and update godaddy DNS. This is okay however only if you can allow for some outage time between changes. (The DNS will take time to Propagate up to 24 hours)
Upgrade your noip account to a plus managed DNS it costs $29.95 a year. However it will allow you to bring your own domain name from another provider like go daddy. Depending how often your noip client is running there could be a very small outage between changes.
https://www.noip.com/support/knowledgebase/can-i-use-my-own-domain-name-with-no-ip/
Good Afternoon,
I wanted to ask this question regarding SSL certificates. Our company manages several servers. For example:
location1.domain.com
location2.domain.com
location3.domain.com
Each of the links goes to a different server with different IP as it pertains to connecting to the system from the outside world. And at each location, there are browsers that connect to each server on the local network to the same network.
For example:
192.168.2.130
The server is an apache2 running ubuntu server 14. In addition, in all the tutorials that I have looked at, one needs to know the IP address of the machine. With many of these locations, the IP address often changes. They have dynamic IPs. What I was wondering is what kind of SSL certificate do I need? I thought about the wildcard certificate but did know if it was an overkill. I also would like for the location users within each location to not see the error message that comes from not having a correctly signed SSL certificate. Thanks in advance.
George
Unless the number of location is constantly changing, you don't need a wildcard certificate. Just get one per location. Certificates should always be assigned to a name, not ip, so how the request is routed doesn't really matter.
If the internal users actually connect via IPs, rather than names, that's something you need to fix, because you have to bind the certificate to a stable name. If you want the internal users to skip the global routing, you can use something like split-horizon dns for it. (basically you serve your local users different dns answers than the ones you publish to the internet)
I just want to know, how to view camera over the internet. I dont have static IP so that can be the problem, because the dynamic ip can be changed and I have to use DDNS.
But as I know, the dynamic IP doesnt change so often, so will it works (watch camera through internet) with the nonchanging dynamic IP? Or the DDNS does something more than just updating IP into domain.
Thanks a lot.
This might not be the right board for this question, but as I use the same service for various things, I'll take a stab at answering your question.
Services like DynDNS an other DDNS providers exists for the sole reason, as you mentioned, of updating an IP address to a domain name. This is useful in instances, like remote camera viewing, where you may or may not know the WAN IP address of the camera's location.
Usually, cable ISPs will not update your WAN IP address very often, so a DDNS service might not seem like a necessity. That could come back to bite you though if you're traveling and your ISP does update your WAN IP address.
Most DSL ISPs update your WAN IP address fairly often, so in those instances, a DDNS service would be more useful as you would have access to your camera regardless of the WAN IP address where it is located.
So all that said, the real answer comes down to your specific requirements. Hope that helps!
I'm currently beginning to learn Apache. So I'm really a beginner here. I've been able to set up a basic site and virtual hosts that I can access within my own network.
Forgive me if my question sounds stupid but is it possible to access my virtual hosts via name-based virtual hosting using only my external IP? Or would I have to have an actual registered domain name for my virtual hosts that will be mapped by DNS to my external IP?
I might have answered my own question here. But I dunno. I'm a total noob here.
Thanks!
You can serve multiple domain-names off of a single IP, though IMO it is always best practice to have separate IP's for each domain/subdomain you want to use, as over time you might need to move domains around across different servers. In these cases you can (if your hosting set up allows) move the IP address along with the site you are migrating without having to update DNS.
While it's not a good permanent solution, PageKite is a neat service that could help you out
Hi everyone I'm a new apache tomcat user I have question regarding seting up a domain name I'm kinda confused about that and how do I know what is my current domain name? can I change the domain name ? I looked into the apache documentations but it was not clear
Thank you in advance
Lava
This question sounds a lot like it's asking about domain name registration and DNS hosting rather than anything tomcat specific.
Your current domain name is probably given to you by whoever hosts your server if you're using public address space. If it's a Unix/Linux box you can find out what that is (assuming things are configured sanely) from a shell using
hostname -A
If you only know the IP address you can make a reverse lookup to find a DNS name that probably points back to your server.