| HTML |
|---|
<div id="google_translate_element"></div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en'}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script> |
Configuring Secure64 Support
| Table of Contents |
|---|
| Note | ||
|---|---|---|
| ||
6connect uses port 22 to communicate with Secure64 infrastructure - please ensure that this is addressed in any ACLs/firewalls |
...
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 |
...
| Note |
|---|
[authdnsadmin@Secure64DNS]# cat 6connect_nsd.conf AutoGenerated by 6connect ProVision. Do not manually edit. zone: name: atestzone.com zonefile: /test12/6connectGeneric/m/atestzone.com.zone zone: name: Testzone2.com zonefile: /test12/6connectGeneric/m/Testzone2.com.zone |
...
In the example above, 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 |
...
Step 7: Validate Zone data in Your Infrastructure
...