Differences

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

--- blocks:server:advanced_server_configuration:dns_server [2023-03-14 10:36]
mattias created
+++ blocks:server:advanced_server_configuration:dns_server [2024-10-25 08:01] (current)
admin Obsolete
@@ Line 1: / Line 1: @@
+:!: **IMPORTANT**: This document is obsolete and describes an older version of out linux server. The current method is [[blocks:server:advanced_server_configuration:dhcp_dns_server|described here here]].
 ===== DNS Server =====
@@ Line 13: / Line 15: @@
 {{ :blocks:adv-conf:dns_a_records.png?nolink |}}
-The name "pixi.guide" is pre-configured pointing to the IP address of the BLOCKS server (here assuming that the server is configured as set up in the [[First Start]] article). If you use a different address for the server on your network, it must be changed accordingly here.
+The name "pixi.guide" is pre-configured pointing to the IP address of the BLOCKS server). If you use a different address for the server on your network, it must be changed accordingly here.
 :!: There's also an alias (CNAME) record  named "int.pixi.guide" that points back to "pixi.guide", which is used in some cases and should be left in place.
@@ Line 31: / Line 34: @@
 {{ :blocks:adv-conf:dns_apply_config.png?nolink |}}
+==== Enabling and Starting the DNS Server ====
+To start your DNS server, and to make sure that it will start automatically if the server is restarted, select "Bootup and Shutdown" under System in the menu on the left-hand side. Once the list of services appears, type //named// into the filter field in the top right hand corner to see only relevant services. Put a checkmark next to "named.service" and "named", as shown below, then click "Start Now and on Boot". Return to this page, filter on //named// again, and verify that both the "Start at boot" and "Running now" columns read "Yes" for the services you just enabled.
+{{:blocks:server:advanced_server_configuration:namedrunning.png?nolink&1000|}}
+==== Create a new DNS Zone Master Record ====
+This article is related to a general network topic outside the scope of blocks. We strongly recommend that you consult with a network professional for assistance in this area.
+To use your own domain name, add a Zone Master Record. If visitors can use their own devices for accessing your server by this name, use a domain name that you own. You can then also publish instructions on an internet-accessible web server advising visitor to log on to the local wifi first.
+In this example, we'll add the “my.guide” domain, which will work alongside the default "pixi.guide" domain.
+Start by logging in to webmin, by entering [your servers IP address]:10000 into the address field of your browser. If you do this from a browser on the server itself, you can type //localhost:10000// into the address field. Log in as pixi-admin. Select Servers/BIND DNS Server in the left-hand menu.
+{{:blocks:adv-conf:bind_server.png?nolink&1000|}}
+Click the Create master zone button, then enter your domain name, the server address and an email address.
+{{:blocks:server:master_zone_record.png?nolink&1000|}}
+Finally, click the "Create" button. You have now created a Master Zone, now we need to add a A-record to the zone. This is done by clicking the new Master Zone Records icon, then click the Address button.
+{{:blocks:server:address_button.png?nolink&1000|}}
+Enter your domain name and the IP address of your server and click create.
+{{:blocks:adv-conf:a_record.png?nolink&1000|}}
+Finally, restart the DNS-server or the computer. (This can be done in webmin, System/Bootup and shutdown, search for named, select named.service and click the restart button).
+====Update DNS records for a new server IP address====
+If you change the IP address of computers on the network you wish to reach by name, you must also make the corresponding changes to the DNS records for those computers.
+  * Use Webmin.
+  * Select //BIND DNS Server// under the Servers heading on the left hand side.
+  * Click the //pixi.guide// zone button.
+{{:blocks:adv-conf:bind_dns_server.png?nolink&1000|}}
+  * Click the Addresses button.
+{{:blocks:adv-conf:edit_master_zone.png?nolink&1000|Image Edit master zone.png}}
+  * Click the pixi.guide. record to open the edit window.
+  * Enter the desired IP address.
+  * Click save.
+{{:blocks:adv-conf:address_records.png?nolink&1000|Image pixi.guide address record}}
+Restart the DNS server by clicking the "rotary arrow" button in the top right hand corner of the main "BIND DNS Server" page.
+==== Verify Operation of the DNS Server ====
+To verify that the DNS server is running and response properly, open a terminal window on a separate computer on the same network, and type
+''nslookup pixi.guide''
+This will attempt to look up the name given to the server. If your other computer is indeed using your newly configured DNS server, it should look up the name there, and give you a result like this.
+{{:blocks:adv-conf:dnsverify.png?1000;nolink}}
+This response provides you with the following information:
+  * The server being used is at address 10.2.0.10 (which is the address of the BLOCKS server, now also acting as a DNS server).
+  * The adress being resolved for the name "pixi.guide" is 10.2.0.10 (again, the address of the BLOCKS server).
+Here are some things to check if you don't get the expected response:
+  * Ensure that your separate computer is connected to the same network as the server (open a terminal window and type "ping 10.2.0.10" to verify that it reaches the server).
+  * Are you using the BLOCKS Server as the DHCP server, as described earlier in this article? If so, it should provide your separate computer with its own IP address as the DNS adress. See under [[#Verify Operation of the DNS Server]] above.
+  * Are there other enabled network interfaces on your separate computer? If so, that network can specify another DNS which may take precedence. This will be indicated by the Server address shown not being the IP address of the local BLOCKS server. If so, disconnect that network and try again.