...
| Code Block | ||
|---|---|---|
| ||
[authdnsadmin@Secure64DNS]# cat nsd.conf server: ip-address: 50.198.192.138 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 |
...
server:
ip-address: 50.198.192.138
axfr-logfile: /axfr_log/axfr.log
axfr-logfile-flush-count: 1
axfr-logfile-max-size: 100000
axfr-logfile-max-size: 10
...
Step 2: Make a directory for 6connect ProVision to push zone files to on the Secure64 DNS Server
| Code Block |
|---|
include: 6connect_nsd.conf
...
[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 6connect ProVision for your Secure64 DNS Server
Go to the
...
6connect Admin area and click on the DNS Admin
...
Tab. Click on the New Server
...
button.
...
Then fill in the information as follows (including any relevant SOA information):
Step 4: Test the Secure64 DNS Server configuration
Press the Test Config button for the DNS Server you setup.
Hit Test Config
Success! Will show as depicted above.
Click add server Add Server to add this server as a permanent entry in the dropdown menu. This server will now be available for assigning DNS zones to.
Step 5: Assign any imported/existing zones to your Secure64 DNS Server(s)
Search for all available zones or enter in a value to find specific existing zones in the system.
| Info | ||
|---|---|---|
| ||
No character in the search area indicates a search for all zones as shown below |
.
Select the Select Server and as Master Tabs to assign the above zones to this server.
Verify the DNS Zones Tranfers area indicates your server and the # of zones to transfer. Hit the 3 Zones box and Push to transfer zones to this server.
The system will present the following live progress bar and show as follows when it is finished without errors. 
Towards the bottom of the progress status will be the final indication of success or errors to correct.
The result of the Push can be checked/verified by checking the Secure64 server as follows:
ssh to 50.198.192.138
Login using rdonnelly/secure64
Enable cachednsadmin
Ls
Verify that the 788 2013-08-21 12:35:04 6connect_nsd.conf file now exists.
[authdnsadmin@eval138.secure64.com]# ls
/:
6728 2013-08-13 00:15:30 nsd.conf
8416071 2013-08-21 12:35:07 nsd.db
788 2013-08-21 12:35:04 6connect_nsd.conf
﹤DIR﹥ 1024 2013-08-21 12:34:50 test12
You can verify the Push contents by doing a cat of the 6connect_nsd.conf
[authdnsadmin@Secure64DNS]# cat 6connect_nsd.conf
...