User Tools

Site Tools


ubuntu:bind:configure_bind9:primary_nameserver

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
ubuntu:bind:configure_bind9:primary_nameserver [2020/12/09 14:37] – [Reverse Zone File] peterubuntu:bind:configure_bind9:primary_nameserver [2020/12/09 17:59] (current) – [Forward Zone File] peter
Line 24: Line 24:
 </code> </code>
  
-Edit the new zone file **/etc/bind/db.example.com** and change **localhost.** to the FQDN of your server, leaving the additional . at the end. +Edit the new zone file **/etc/bind/db.example.com** as follows:
- +
-Change 127.0.0.1 to the nameserver’s IP Address and root.localhost to a valid email address, but with a . instead of the usual @ symbol, again leaving the . at the end. Change the comment to indicate the domain that this file is for. +
- +
-Create an A record for the base domain, example.com. Also, create an A record for ns.example.com, the name server in this example:+
  
 <file bash /etc/bind/db.example.com> <file bash /etc/bind/db.example.com>
Line 48: Line 44:
 </file> </file>
  
-<WRAP important+<WRAP info
-**IMPORTANT:**  The Serial Number must be incremented every time changes are made to a zone file.+**NOTE:**  
 + 
 +  * **Comment:**  Change this comment to refer to the domain that this file is for. 
 +  * **Serial Number:** <WRAP important> 
 +**must** be incremented every time changes are made to a zone file.
  
 This Serial number can simply be any number, such as 1 or 2 or 3 etc. This Serial number can simply be any number, such as 1 or 2 or 3 etc.
  
 The approach taken here is to use the last date this zone file was edited, in the format yyyymmddss (where ss is the change number for that day; 01 for 1st change, 02 for 2nd change, etc). The approach taken here is to use the last date this zone file was edited, in the format yyyymmddss (where ss is the change number for that day; 01 for 1st change, 02 for 2nd change, etc).
- 
 </WRAP> </WRAP>
 +  * **FQDNs:** <WRAP important> 
 +Leave the additional **.** at the end of the FQDNs (example.com. and root.example.com.). 
 +    * **root.example.com.** actually refers to an email address of root@example.com.  Change this as needed to a valid email address, but with a . instead of the usual @ symbol, and leaving a . at the end. 
 +</WRAP> 
 +  * Create an **A** record for the base domain, example.com. 
 +  * Create an **A** record for the nameserver; in this example **ns.example.com**. 
 +</WRAP> 
 + 
 <WRAP info> <WRAP info>
-**NOTE:**  Add any DNS records to the bottom of the zone file.+**NOTE:**  Add any additional DNS records to the bottom of the zone file.
  
-See Common Record Types for details.+See [[[[Networking:DNS:Common Record Types|Common Record Types]] for details.
 </WRAP> </WRAP>
  
Line 74: Line 80:
 ===== Reverse Zone File ===== ===== Reverse Zone File =====
  
-A Reverse Zone needs to be added to allows DNS to resolve an address to a name.+A Reverse Zone needs to be added to allow DNS to resolve an address to a name.
  
 Edit **/etc/bind/named.conf.local** and add the following: Edit **/etc/bind/named.conf.local** and add the following:
Line 88: Line 94:
 **NOTE:**  Replace 1.168.192 with the first three octets of whatever network you are using. **NOTE:**  Replace 1.168.192 with the first three octets of whatever network you are using.
  
-Also, name the zone file /etc/bind/db.192 appropriately.  It should match the first octet of your network.+Also, name the zone file **/etc/bind/db.192** appropriately.  It should match the first octet of your network.
  
 </WRAP> </WRAP>
ubuntu/bind/configure_bind9/primary_nameserver.1607524631.txt.gz · Last modified: 2020/12/09 14:37 by peter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki