We provide free web hosting. (South Korea)

I am a university student and I am running a home server with an i7-13700K. I have so many server resources left over and I want to offer free hosting to one person.





PC Info
• Server Location: South Korea
• CPU: i7-13700K
• RAM: 64GB
• Storage: PCIe 4.0 SSD (PM9A1 1TB)

Offer List
• Web site (Apache, PHP 7.4/8.0/8.1) (1 site, 5GB)
• DB(MariaDB) (1 DB, 5GB)
• FTP (1 FTP, 30GB)
• Backup
• Web Control Panel (1 User)
• 10GB traffic (Day) (500 Mbps)

If you want to apply for web hosting, please write down the purpose of using it in the comments. We will select one person and guide you through the comments.

Points to Note
• I am a person studying IT. It’s not as perfect as paid hosting.
• OS security updates may cause site downtime.
• The service is provided with a dynamic IP, not a static IP. (Please use CNAME.)
• Only personal sites are allowed.
• Religious sites are prohibited.
• Operating illegal sites is prohibited.

 

There are also ARM servers. It's slow, but it's enough to run a small website. The ARM server will accept applications for 5 users.

 

Chingu, annyong!
Why do you want, that somebody join your server, what for?

And could you explain, how to acquire domains to be accessible to www without server' ip?

All my knowledge - static ip connection (of what i had learnt from HowtoForge tutorials).

How do you glue it by means of canonical names?

 

This is not true. We need a public IP for a server to be accessible on the internet, but it need not be a static / fixed IP. He already noted the use of cname of which you can get via various free or paid dynamic IP services, but with certain limitation of course.

 

yes... but how it works
i have caught myself on idea, that do not understand whole technology of even with static ip's too

 

An example would be running a server from home where the public IP provided by the ISP is normally dynamic IP. Anyway, good luck learning it as I am not here to teach.

 

Okay, will wait for my own Master Yoda

 

(Translated from Korean to English.)
In dynamic IP, paid services are virtually impossible. And I'm still learning the software, so I need more knowledge to offer it for a fee.

 

Server's public IP exists. However, it is a dynamic IP, not a static IP.

If I set the A record to a static IP, there is no problem. However, if you set the A record to a dynamic IP, you will have to change the IP of the A record each time when the IP is changed. It's a very cumbersome task.

A solution to this problem is CNAME.

We will briefly explain the principle.

A Record
Domain <> Server IP

CNAME
Domain <> *.duckdns.org <> Server IP

If you set the domain as a CNAME, DDNS (DuckDNS, etc.) address, it will be mapped to the server IP. This approach offsets the disadvantages of dynamic IP.

If you want to know more, look up CNAME, DDNS.

 

Bro, what are you talking about?
- i didn't mean any of paid services
But i have asked: - Why do you need, that somebody reside at your server?

And, please, write down straightforwardly in korean

 

My man, could you provide screenshots, describing the whole structure?

 

한국에는 여러 무료 웹 호스팅이 존재합니다. 그 중 모든 서비스를 무료로 제공하는 웹 호스팅이 존재합니다. 어떠한 유료 서비스도 존재하지 않습니다. 글을 작성하면 포인트가 적립되는데 포인트로 웹 호스팅을 사용할 수 있습니다. 제가 여기에서 감명을 받아 무료 웹 호스팅을 제공하고 싶습니다.

 

DDNS를 사용하는 대표적인 방법은 공유기의 DDNS 기능이나 DDNS 프로그램을 이용하는 것입니다. 그 중 Duck DNS 프로그램으로 설명드리겠습니다.

• https://www.duckdns.org/
Duck DNS를 사용하기 위해서 Duck DNS 사이트에 접속해서 로그인하고, 서브 도메인을 입력한 뒤 'add domain'을 클릭하여 *.duckdns.org 도메인을 발급받습니다.

• https://www.duckdns.org/install.jsp
가이드를 따라 운영체제에 Duck DNS 프로그램을 설치하고 설정을 완료하면 *.duckdns.org 도메인이 서버 IP를 A 레코드로 연결합니다.
(서버 IP 변경 사항은 Duck DNS에 자동으로 반영됩니다.)

• 도메인을 CNAME, *.duckdns.org로 설정하면 서버 IP로 연결됩니다. (Domain <> *.duckdns.org <> Server IP) (이는 도메인이 서버 IP를 A 레코드에 연결하도록 하는 것과 동일한 효과가 있습니다.)

 

정확한 번역 결과를 원하면 DeepL을 사용하세요.
https://www.deepl.com/translator

 

Dear Mr. Till und Mr. Th0m, many thanks!!!
My apologies, i didn't know about a mandatory rule to write in english... and that guy @kcafe703 has been induced by me for that action

Needless to say, i also consider his explanation as an unpersuasive:

1. did not hear, that there is lot of free web-hosting in Korea
2. idea of earning points - also looks doubtful
3. and of being impressed by what?

Definitely, every of us should realize, that placing your data anywhere is a process, when you must rely to a party's ethics.

But what i love about this member, that he diligently tried to explain me, what i had asked.

 

Okay, let's assume, i have somewhat ~domain name, called timmehosting.de @ inwx.com


and must to point out nameservers:
ns1&ns2 either dns1&dns2

Hence, on the server-side these subdomains must be created - ns1.timmehosting.de & ns2.timmehosting.de.

Centos 7 structure:
- /etc/named.conf

Expand: named.conf

options {
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { any; };
allow-recursion {"none";};
recursion no;
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "." IN {
type hint;
file "named.ca";
};
include "/etc/named.conf.local";

- /etc/named.conf.local

Expand: named.conf.local

zone "timmehosting.de" {
type master;
file "/var/named/pri.timmehosting.de";
};

- /var/named/pri.timmehosting.de

Code:

$TTL        3600
@       IN      SOA     ns1.timmehosting.de. trade.timmehosting.de. (
                        2023021201       ; serial, todays date + todays serial #
                        7200              ; refresh, seconds
                        540              ; retry, seconds
                        604800              ; expire, seconds
                        3600 )            ; minimum, seconds
;

timmehosting.de. 3600      A          normally.static.ip.here
mail 3600      A          normally.static.ip.here
ns1 86400      A          normally.static.ip.here
ns2 86400      A          normally.static.ip.here
www 3600      A          normally.static.ip.here
timmehosting.de 3600      AAAA       normally:static:ip:version:6:here
www 3600      AAAA       normally:static:ip:version:6:here
pop3 86400      CNAME      mail.timmehosting.de
timmehosting.de. 3600      CAA        0 issue "letsencrypt.org"
timmehosting.de. 3600      MX     10  mail.timmehosting.de.
timmehosting.de. 3600      NS         ns1.timmehosting.de.
timmehosting.de. 3600      NS         ns2.timmehosting.de.
timmehosting.de. 3600      TXT        "v=spf1 mx a ~all"

$INCLUDE Ktimmehosting.de.+013+09077.key
$INCLUDE Ktimmehosting.de.+013+12844.key

Ubuntu 18 Bionic structure - /etc/bind:
named.conf

Expand: /etc/bind/named.conf

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";

named.conf.options

Expand: /etc/bind/named.conf.options

options {
directory "/var/cache/bind";

version "unknown";

allow-transfer {none;};

auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};

named.conf.local

Expand: /etc/bind/named.conf.local

zone "timmehosting.de" {
type master;
file "/etc/bind/pri.timmehosting.de";
};

pri.timmehosting.de

Code:

$TTL        3600
@       IN      SOA     ns1.timmehosting.de. mail.timmehosting.de. (
                        2023012401       ; serial, todays date + todays serial #
                        7200              ; refresh, seconds
                        540              ; retry, seconds
                        604800              ; expire, seconds
                        3600 )            ; minimum, seconds
;

timmehosting.de. 3600      A          normally.static.ip.here
www 3600      A          normally.static.ip.here
mail 3600      A          normally.static.ip.here
ns1 86400      A          normally.static.ip.here
ns2 86400      A          normally.static.ip.here
timmehosting.de. 3600      NS         ns1.timmehosting.de.
timmehosting.de. 3600      NS         ns2.timmehosting.de.
timmehosting.de. 3600      MX     10  mail.timmehosting.de.
timmehosting.de. 3600      TXT        "v=spf1 mx a ~all"

For such an occasion, not having normal static ip, what do you have to put inside of /etc/hosts?

And don't you know, how Dynamic DNS service is acquired namely to your network adapter? - through MAC-address?

 

your last image looks like dealing on the network-guard' side - to protect your whole connection to www

 

In dynamic dns you use fixed / static local IP as prescribed in PST. You set your router to forward all relevant ports to that local IP or alternatively you put it in DMZ of that router so it is publicly accessible but only with its own firewall to protect. Note that not all services will work like mail but others can be worked out. Web service is one of the easiest thing to be done using public dynamic IP.