Self-hosting: Difference between revisions

(2 intermediate revisions by the same user not shown)

Line 1:

[[File:Server rack interconnects work in progress - IMG 3473.jpg|thumb|Server rack interconnects work in progress]]

When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.

Line 13:

Line 15:

When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.

<small>Note: You might already have seen the term DNS in your router or network settings. It's the same concept. The public/free DNS service you use on your computer is what your browser, etc will use to find out IP addresses of websites you want to visit. But even that DNS service needs to know how to answer a request for your domain. And therefore you need an "authoritative" DNS server which is configured with the right answer. This is often provided by the registrar themselves, but you can also have a service provider different from your registrar be your authoritative DNS server. DNS servers talk to each other. Therefore, even if you have a different DNS server on your router/network, it will eventually ask your authoritative DNS server for the answers.</small>

You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.

Line 85:

Line 89:

* [[Sysadmin roadmap]]

== External Links ==

* [https://www.keithcirkel.co.uk/a-playbook-for-hosting-simple-services/ How I host websites] — blog post by Keith Cirkel, engineer at Mozilla

@@ Line 1: / Line 1: @@
+[[File:Server rack interconnects work in progress - IMG 3473.jpg|thumb|Server rack interconnects work in progress]]
 When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.
@@ Line 13: / Line 15: @@
 When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.
+<small>Note: You might already have seen the term DNS in your router or network settings. It's the same concept. The public/free DNS service you use on your computer is what your browser, etc will use to find out IP addresses of websites you want to visit. But even that DNS service needs to know how to answer a request for your domain. And therefore you need an "authoritative" DNS server which is configured with the right answer. This is often provided by the registrar themselves, but you can also have a service provider different from your registrar be your authoritative DNS server. DNS servers talk to each other. Therefore, even if you have a different DNS server on your router/network, it will eventually ask your authoritative DNS server for the answers.</small>
 You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.
@@ Line 85: / Line 89: @@
 * [[Sysadmin roadmap]]
+== External Links ==
+* [https://www.keithcirkel.co.uk/a-playbook-for-hosting-simple-services/ How I host websites] — blog post by Keith Cirkel, engineer at Mozilla