PIXILAB Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
blocks:server:advanced_server_configuration:dhcp_dns_server [2025-05-08 14:16] – [Configuration] adminblocks:server:advanced_server_configuration:dhcp_dns_server [2025-11-11 09:04] (current) – [DPCP and DNS server] mattias
Line 1: Line 1:
-=====DPCP and DNS server=====+=====DHCP and DNS server=====
 Your linux based Blocks server comes with software letting it can act as a DHCP and/or DNS server for your local network. A DHCP server provides automatic addressing to PIXILAB Player and other network devices set to use automatic addressing. The DNS allows for local name resolution, such as resolving the doman name pixi.guide to the IP address of your server. Using service names rather than raw IP addresses makes it easier to change addressing in the future and is also required for some advanced functions, such as encrypted connections ([[blocks:server:https|HTTPS]]). Your linux based Blocks server comes with software letting it can act as a DHCP and/or DNS server for your local network. A DHCP server provides automatic addressing to PIXILAB Player and other network devices set to use automatic addressing. The DNS allows for local name resolution, such as resolving the doman name pixi.guide to the IP address of your server. Using service names rather than raw IP addresses makes it easier to change addressing in the future and is also required for some advanced functions, such as encrypted connections ([[blocks:server:https|HTTPS]]).
  
Line 60: Line 60:
   * **interface=eno1** specifies which network interface to bind the DHCP/DNS service to. Verify that the name specified here matches the correct network interface on your server using the **ip a** command from within a terminal window to list all interfaces.   * **interface=eno1** specifies which network interface to bind the DHCP/DNS service to. Verify that the name specified here matches the correct network interface on your server using the **ip a** command from within a terminal window to list all interfaces.
   * **dhcp-range=10.2.5.1,10.2.10.254,12h** specifies the range of dynamically assigned IP addresses, and their "lease time". The range shown in the example above is appropriate for the default server IP address 10.2.0.10 with netmask 255.255.0.0 (a class-B internal network). Adjust this as appropriate if you use another server address and/or netmask.   * **dhcp-range=10.2.5.1,10.2.10.254,12h** specifies the range of dynamically assigned IP addresses, and their "lease time". The range shown in the example above is appropriate for the default server IP address 10.2.0.10 with netmask 255.255.0.0 (a class-B internal network). Adjust this as appropriate if you use another server address and/or netmask.
-  * **dhcp-option=option.** The netmask dns-server and router options are passed on to DHCP clients to set these values automatically. The netmask and dns-server options must match your server's wired network settings.+  * **dhcp-option=option.** The netmask, dns-server and router options are passed on to DHCP clients to set those values automatically. The netmask and dns-server options must match your server's wired network settings.
  
 Other settings may be [[https://wiki.archlinux.org/title/Dnsmasq|configured or added]] as desired. Other settings may be [[https://wiki.archlinux.org/title/Dnsmasq|configured or added]] as desired.
  
-Click the "Save and close" at the bottom of the page once you're done. The select "Test DNSMASQ configuration" to validate your configuration file. If any errors are reported, you must go back and fix those before proceeding.+Click the "Save and close" at the bottom of the page once you're done. Select "Test DNSMASQ configuration" to validate your configuration file. If any errors are reported, you must go back and fix those before proceeding.