Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I know Route53 is dirt-cheap - but for those who are purists about "free", you can do the same thing with Hurricane Electric's DNS service (dns.he.net).
Second IP address / server is not "required".Those were very helpful. The "howto" link mentioned that if I were to setup my own DNS server, I'd need two static ip addresses, mainly so I could have a primary and secondary server. Is that absolutely necessary? Is it possible to set this up with only one DNS server, since I really don't want to pay for a 2nd IP address?
I understand this, but I am looking for a learning experience more than anything, so setting up my own DNS server is not out of the picture!Second IP address / server is not "required".
Your best bet is to use a service that is designed for this.
I understand this, but I am looking for a learning experience more than anything, so setting up my own DNS server is not out of the picture!
Good deal. You chose a good registrar. There are a lot of crappy ones that lock down their DNS and try to use that to force you into buying their other 'services'.So, just an update, this ended up being a very simple process. The company I purchased the domain through, and host some website with, allowed me to create a zone file pointing to the ip address, and in a few minutes, the name points to the web server! No need for 3rd party anything. Now, hopefully my IP address will continue to stay the same as it has the past three years.....
Good deal. You chose a good registrar. There are a lot of crappy ones that lock down their DNS and try to use that to force you into buying their other 'services'.
Mind sharing who the registrar was (and I understand if you want to keep it private).
I have no problem sharing the registrar, kinda like to promote companies that provide good server. Namepal.com is the site.
Now, I've run into a slightly different problem. Not sure if it's the DNS entry or the Apache config file. The issue is, to access the site, I have to use the full URL: "https://www.mydomain.com" If I leave off the https://, can't access the site. Can't access the site if I leave off the "www." either.
Just in case anyone wants to look at this, in my httpd.conf file, I have the server set to listen only on port 443, and I have the server name set as www.mydomain.com:443
My DNS zone file has the host as www.mydomain.com, origin is mydomain.com. I'm not sure if the host should just be "www" instead of the full name.
I'll be doing some more experimenting and research, it isn't a big deal right now, but something I'd like to figure out why.