If you like DNray Forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...

 

How to organize the Internet at home with domain?

Started by dinuanzz, Mar 01, 2023, 07:51 AM

Previous topic - Next topic

dinuanzzTopic starter

We need to set up a local network with the domain name .dom.

For the nettop server, we will use the Lenovo q180 with Ubuntu Server 13.04 without GUI.
We receive internet from the TP-LINK TL-WR741N router via Wi-Fi.

Currently, I access the server resources using the following addresses:
192.168.137.142/redmine
192.168.137.142/phpmyadmin
192.168.137.142/dev_project
192.168.137.142/rc_project

I would like to access them like this:
redmine.dom
phpmyadmin.dom
dev.project.dom
rc.project.dom

Please provide me with articles, manuals, or an overview of how to set this up.
Or give me guidance on where to start. As a newcomer to Linux, any help would be appreciated :)

Thank you for your assistance!
  •  

jacoblin

The easiest and most cost-effective solution is to register the hosts file on every machine. On Windows, it is typically located at %windir%\system32\drivers\hosts, and on Linux, it can be found at /etc/hosts. Inside the file, add the following line: "dom 192.168.137.142".

To configure multisite setups in Apache, you need to create separate configurations for each type and specify the DOCUMENT_ROOT for each desired folder. This can be done in the /etc/apache2/site-available/default file. Simply copy the existing structure multiple times and modify the parameters accordingly.

Another option is to duplicate the site under a different name, adjust the parameters, and start the configuration registration using the command "<b>$>a2ensite newfilename</b>".

After restarting Apache, the changes should take effect. However, if any issues arise, you can examine the Apache logs and make the necessary adjustments.
  •  

lalmazl

Here is the usual approach:
First, set up a DHCP server on either a router or a home server to distribute a private IP address range like 192.0/16, along with a domain name such as blabla.local (note that there are reserved names for internal use that can be found through research).

Next, give each machine a hostname in the format host.local, host1.local, or any other chosen naming convention.

Then, configure a DNS server where you can manually register hosts or retrieve them from a DHCP database. For example, you can set static entries for mysql.local, ftp.local, and other services.

Finally, configure Network Address Translation (NAT) to map incoming IP:port to the corresponding IP:port in the internal network. It's worth noting that NAT does not consider the domain; it only focuses on the mapping of IP and port numbers.
  •  

thietkeweb3s

To establish a DNS server on your server, such as BIND for Ubuntu, you can find numerous articles detailing the setup process. Configure the server as a master server for the .dom zone and set it to forward requests to the DNS provider for other zones.

On the DHCP server, assign the address of your DNS server to all clients. You should be able to handle the configuration of virtual domains on Apache.

However, it's worth noting that the idea of using the .dom zone may not fully align with standards. While it will still function correctly, it's advisable to utilize the dom.local zone for better compliance.
  •  

Boireanaria

To set up a local network with the domain name .dom, you will need to configure a DNS server on your network. Here are the steps to achieve this:

1. Install and configure a DNS server: You can use Bind as your DNS server. Install it using the package manager on your Ubuntu Server. Once installed, configure the DNS server by editing the configuration files.

2. Set up the DNS zone: Create a new zone file for your .dom domain in the Bind configuration directory. You can name the file "dom.zone" or any other name you prefer. In this file, define the IP addresses corresponding to the domain names you want to use.

3. Configure the DNS server to use the zone: Edit the main Bind configuration file (/etc/bind/named.conf) and add an entry to include your new zone file. The configuration entry should look like this:

zone "dom" {
    type master;
    file "/etc/bind/dom.zone";
};

4. Configure your local network devices: You need to update the DNS settings on your local devices to point to the IP address of your DNS server. You can usually do this through the router's administration page or by manually configuring the DNS settings on each device.

5. Test the setup: Restart the Bind service to apply the changes. Then, try accessing the server resources using the new domain names (e.g., redmine.dom). If everything is set up correctly, you should be able to access them without any issues.

I would recommend referring to the official Bind documentation or searching for tutorials online for more detailed instructions on setting up a DNS server. You can also find helpful resources on Ubuntu's community forums or websites like DigitalOcean.

As a newcomer to Linux, you may also find it beneficial to familiarize yourself with basic Linux networking concepts and commands. Understanding how networking works in Linux will help you troubleshoot and configure your network effectively.

Good luck with your setup, and I hope this information helps you get started!
  •  


If you like DNray forum, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...