Differences

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

--- computing:ispconfig [2023/05/21 22:46] – oemb1905
+++ computing:ispconfig [2023/05/21 22:57] (current) – oemb1905
@@ Line 3: / Line 3: @@
   * **Jonathan Haack**
   * **Haack's Networking**
-  * **netcmnd@jonathanhaack.com**
+  * **webmaster@haacksnetworking.org**
 -------------------------------------------
@@ Line 75: / Line 75: @@
 Make sure to record the mysql and ispconfig database passwords for each securely. Be sure to select expert mode and be sure to use the local address of the primary, 192.168.122.1, not the external for mysql communcations. Use the securepassword you chose while setting up the database above for the primary. Make sure you say "n" to adding the web panel and/or other services not needed for DNS. Next, we need to log in to the web panel of the primary server and go to Settings / ns2.haacksnetworking.com and Settings / ns3.haacksnetworking.com and change the "Is mirror of Server" dropdown to ns1.haacksnetworking.com.  Once that's done, we can now set up our zone on ISP Config and the Glue records on the Registrar.  To set up your zone, go to DNS / Add new DNS zone with Wizard on the web panel, and enter your domain, the IP of your primary name server, and for the nameservers enter ns1.haacksnetworking.com and ns2.haacksnetworking.com. Enter an email of your choice and select create zone. You need to now add a third NS record for your other name server, and don't forget the trailing "." as this will cause hours of caching errors. Secondly, make sure to create three corresponding A records for each domain (ns1, ns2, ns3) that point to the IPs of those domains. Once all the zone is added as follows and all records entered properly, check ''/etc/bind/'' and make sure there is no ''.err'' appended to ''pri.haacksnetworking.com''. If there is, you likely parsed something wrong while entering the records. Adjust and debug until the error goes away when you restart bind9's service. It's now time to set up the Glue records at your Registrar. To do that, go to your Registrar's Name Server settings, and register name servers for the haacksnetworking.com domain. In the settings, point each of those name servers to the IPs you have set up for them. Once those Glue records are setup, you now change the Name Servers from the Registrar's to your own. Give it a good 1-2 hours to cache, and check this site to see if you did everything correctly:
+[[https://www.whatsmydns.net/#NS/haacksnetworking.com|WhatIsMyDNS]]
+Note everything worked properly at first, and I had to spend some time debugging. Using host and dig can be helpful while debugging:
- --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/05/21 14:00//
+  host ns1.haacksnetworking.com 8.67.82.100
+  host ns1.haacksnetworking.com
+  dig haacksnetworking.com ns
+  dig haacksnetworking.com ns @8.67.82.100
+The commands above check your default dns for the records and/or check the Name Server itself (the one you are setting up now). These commands are particularly helpful in determining whether your name server can return the proper records and/or whether they have already cached to other servers or not. Also, while debugging and re-adding a zone, I did once have to manually remove the ".err" from ''/etc/bind'' and restart bind to get the changes to stick. This is apparently due to a DNSsec glitch in ISPConfig.
+Note: This tutorial is fairly advanced and there are lots of omitted smaller steps, days of debugging that are left unreported and so on. Feel free to email or hit me up on Mastodon (see home page of Wiki) if you need help.
+ --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/05/21 16:46//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools