Versions Compared

Old Version 14

changes.mady.by.user The Force

Saved on

compared with

New Version 15

changes.mady.by.user The Force

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated SS to match test12 condition in text, IP to match SS, changed zone references in code blocks to match SS

...

Code Block
titleOutput/Input
[authdnsadmin@Secure64DNS]# cat nsd.conf 
server:
ip-address: 50.198.192.138141 
 
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

...


Then fill in the information for your Secure64 server (including any relevant SOA information):
Image RemovedImage Added

Step 4: Test the Secure64 DNS Server configuration

Press the Test Config button for the DNS Server you setup.
Image RemovedImage Added

Success! Will show as depicted above.


Click 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.

Image RemovedImage Added

Step 5: Assign any imported/existing zones to your Secure64 DNS Server(s)

...

Note
titleVerifying Zone pushes
ssh to 50.198.192.138141
Login using the designated login account and password
Enable cachednsadmin
ls

...

Note

[authdnsadmin@Secure64DNS]# cat 6connect_nsd.conf

AutoGenerated by 6connect ProVision. Do not manually edit.

zone:

name: mnc016.mcc502.gprs.APNatestzone.com

zonefile: /test12/6connectGeneric/m/mnc016.mcc502.gprs.APNatestzone.com.zone

zone:

name: mnc0016.mcc502.gprs.name4Testzone2.com

zonefile: /test12/6connectGeneric/m/mnc0016Testzone2.mcc502.gprs.name4.zone

zone:
name: epc.mnc016.mcc502.3gppnetwork.org

zonefile: /test12/6connectGeneric/e/epc.mnc016.mcc502.3gppnetwork.org.zone

com.zone

 

In the example above, three two Zones have transferred.

To look at the contents of each zone you can cd to the proper directory /test12/6connectGeneric and find the zone files in an alphabetical directory structure as follows:

...

Info

[authdnsadmin@Secure64DNS]# cd 6connectGeneric

[authdnsadmin@Secure64DNS]# cd test12

changed to test12
[authdnsadmin@Secure64DNS]# ls
/test12/:
﹤DIR﹥ 1024 2013-08-16 19:43:21 6connectGeneric
[authdnsadmin@Secure64DNS]# cd 6connectGeneric
changed to 6connectGeneric
[authdnsadmin@Secure64DNS]# ls
/test12/6connectGeneric/:
﹤DIR﹥ 1024 2013-08-16 17:30:13 e
﹤DIR﹥ 1024 2013-08-16 17:30:16 m
﹤DIR﹥ 1024 2013-08-16 18:49:21 d
﹤DIR﹥ 1024 2013-08-16 19:43:23 s
[authdnsadmin@Secure64DNS]# cd m
changed to m
[authdnsadmin@Secure64DNS]# ls
/test12/6connectGeneric/m/:
[authdnsadmin@eval138.secure64.com]# ls
5192 2013-08-21 15:35:01 mnc0016atestzone.mcc502com.gprs.name4.zone
6758 2013-08-21 15:35:02 mnc016.mcc502.gprs.APNTestzone2.com.zone
284 2013-08-21 15:34:11 m2m.mnc016.mcc502.zone
[authdnsadmin@Secure64DNS]#

...

Info
titleUsing dig to validate your Secure64 Server installation
[authdnsadmin@eval138.secure64.com]# dig @50.198.192.138 mnc0016.mcc502.gprs.name4141 atestzone.com
; ﹤﹤﹥﹥ DiG SourceT 3.x ﹤﹤﹥﹥ @50.198.192.138 mnc0016.mcc502.gprs.name4141 atestzone.com
;; Got answer:
;; ﹥﹥HEADER﹤﹤ opcode: QUERY, status: NOERROR, id: 59591
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;mnc0016.mcc502.gprs.name4atestzone.com. IN A
;; AUTHORITY SECTION:
mnc0016.mcc502.gprs.name4 atestzone.com. 3600 IN SOA ns1.dns.6connect.net. hostmaster.6connect.net. (2013082102 10800 3600 604800 38400 )
[authdnsadmin@eval138.secure64.com]#

...