...
The result of the Push can be checked/verified by checking the Secure64 server as follows:
| Note | ||
|---|---|---|
| ||
| ssh to 50.198.192.138 Login using |
...
| the designated login account and password Enable cachednsadmin |
...
| ls |
Verify Now, verify that the "788 2013-08-21 12:35:04" 6connect_nsd.conf file now exists.
| Code Block |
|---|
[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
| Note |
|---|
[authdnsadmin@Secure64DNS]# cat 6connect_nsd.conf AutoGenerated by 6connect ProVision. Do not manually edit. zone: name: mnc016.mcc502.gprs.APN zonefile: /test12/6connectGeneric/m/mnc016.mcc502.gprs.APN.zone zone: name: mnc0016.mcc502.gprs.name4 zonefile: /test12/6connectGeneric/m/mnc0016.mcc502.gprs.name4.zone zone: zonefile: /test12/6connectGeneric/e/epc.mnc016.mcc502.3gppnetwork.org.zone |
...
In the example above, three Zones have transfered.
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:
[authdnsadmin@Secure64DNS]# cd 6connectGeneric
Could not find directory: 6connectGeneric
[authdnsadmin@Secure64DNS]# cd /6connectGeneric
Could not find directory: /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 mnc0016.mcc502.gprs.name4.zone
6758 2013-08-21 15:35:02 mnc016.mcc502.gprs.APN.zone
284 2013-08-21 15:34:11 m2m.mnc016.mcc502.zone
[authdnsadmin@Secure64DNS]#
Step 8: Validate Zone data n Your Infrastructure
Do a dig of the zones to verify the DNS configuration has been successfully deployed.
[authdnsadmin@eval138.secure64.com]# dig @50.198.192.138 mnc0016.mcc502.gprs.name4
; ﹤﹤﹥﹥ DiG SourceT 3.x ﹤﹤﹥﹥ @50.198.192.138 mnc0016.mcc502.gprs.name4
;; 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.name4. IN A
;; AUTHORITY SECTION:
mnc0016.mcc502.gprs.name4. 3600 IN SOA ns1.dns.6connect.net. hostmaster.6connect.net. (2013082102 10800 3600 604800 38400 )
[authdnsadmin@eval138.secure64.com]#