Configuring Secure64 Support
Table of Contents |
---|
Note | ||
---|---|---|
| ||
ProVision uses port 22 to communicate with and configure Secure64 infrastructure - please ensure that this is addressed in any ACLs/firewalls ProVision also uses port 53 to do zone checks if the DNS Module is enabled and in use. Please ensure that your Secure64 infrastructure is configured to accept DNS lookups from the ProVision server |
S64 Authoritative Server Setup
The initial setup of the Secure64 Authoritative server is as follows:
Step 1: Create an nsd.conf file under the root directory / of your S64 Auth server
Note | ||
---|---|---|
| ||
Make sure to add the line include: 6connect_nsd.conf to the nsd.conf file |
Code Block | ||
---|---|---|
| ||
[authdnsadmin@Secure64DNS]# cat nsd.conf server: ip-address: 50.198.192.141 axfr-logfile: /axfr_log/axfr.log axfr-logfile-flush-count: 1 axfr-logfile-max-size: 100000 axfr-logfile-max-size: 10 request-logfile: /request_log/request.log request-logfile-flush-count: 10 request-logfile-max-size: 1000000 request-logfile-max-files: 10 include: 6connect_nsd.conf |
Step 2: Make a directory for ProVision to push zone files to on the Secure64 DNS Server
Code Block |
---|
[authdnsadmin@Secure64DNS]# mkdir test12 [authdnsadmin@Secure64DNS]# ls /: 322 2013-08-19 06:07:42 nsd.conf <DIR> 1024 2013-08-16 17:30:12 test12 |
Step 3: Setup and Configure ProVision for your Secure64 DNS Server
To create a new server, start from the DNS Tab, select the DNS Servers sub menu. Then, click the "Add Server" button next to "DNS Server List".
...
This will open the "Server Settings" page.
...
1) Set Server Common Settings
...
After entering the server-specific settings in this section, you can click the "Test Connection" button at the bottom right of the page to test the server connection and authentication.
A window will pop up showing a success or failure response.
...
Save your changes when done! Just click the "Save Changes" button at the bottom right of the page.
Step 4: Associate zones to your Secure64 DNS Server(s)
If a default Group was selected while setting up the S64 server, then any zones in that Group will automatically be associated with the server.
...
Info | ||
---|---|---|
| ||
When working with DNS Zones and Records, additional record types may be manually added by selecting "Other" when adding a new record. S64 DNS users can use record type "Other" to add "SYNTH" or "TYPE65464" type records similar to the format below: $ORIGIN 30 IN TYPE65464 ${p4} PTR ${a4}.pool.example.com. $ORIGIN 600 IN TYPE65464 ${a4} A ${a4} $ORIGIN TYPE65464 ${p6} PTR user${a6}.my.example.com. $ORIGIN 5 IN SYNTH user${a6} AAAA ${a6} $ORIGIN IN SYNTH nptr-${u} NAPTR 10 20 "A" "" "" srv-${u} $ORIGIN IN SYNTH srv-${u} SRV 10 20 1234 srv-addr-${u} However, arbitrary / other record types are unable to be validated, so use with care! |
Step 5: Push Zones to Secure64 Server(s)
Navigate back to the DNS tab, and select the "DNS Servers" tab.
Locate the Secure64 server in the DNS Servers list, and then click the "Push" button under "Actions" at the end of the row.
Step 6: Verify DNS Zone push on Secure64 Server(s)
The result of the Push can be checked/verified by checking the Secure64 server as follows:
...
Info |
---|
[authdnsadmin@Secure64DNS]# cd 6connectGeneric [authdnsadmin@Secure64DNS]# cd test12 changed to test12 |
Step 7: Validate Zone
...
Data
Finally, do a dig of the zones to verify the DNS configuration has been successfully deployed.
...
Info | ||
---|---|---|
| ||
When you setup ProVision to communicate via SSH to a Secure64 server, a ley/fingerprint is saved to the local hosts file. If you modify the IP address, but do not clear out the hosts file, then ProVision will think this is an attack and prevent communication with the Secure64 server. To rectify this issue, you may need to reset the host file so that a new SSH host key can be added for the IP address. To do this manually, please follow the following steps: 1) The admin needs to login to the ProVision server via SSH/CLI If you have any issues, please contact 6connect support per your Support Agreement/Plan. |
Additional Information
For additional information on working in DNS, see the following sections:
...