Ticket #6 (closed task: wontfix)

Opened 3 years ago

Last modified 21 months ago

Add post install instructions with screen shot graphics

Reported by: Dylan Owned by: Hugo
Priority: normal Milestone: Change mysql to unxs
Component: unxsBind Severity: Normal
Keywords: unxsApache unxsBind Cc:

Description

Please create unxsBind/iDNS and unxsApache post install "Getting Started" pages.

Should be limited to simple example of creating initial production data for smart.com. Provide screen shots.

Change History

Changed 3 years ago by Hugo

  • status changed from new to assigned

Will do!

Changed 3 years ago by Dylan

  • priority changed from major to normal
  • component changed from documentation to unxsBind
  • severity set to Normal

Changed 3 years ago by Hugo

Let's start writing this now.

Changed 3 years ago by Hugo

Please review what's been written so far here:

http://venus.openisp.net/openisp/unxsVZ/wiki/GettingStartedBind

and send me your comments. Thank you!

Changed 3 years ago by Gary

Ideas:

The links with http://serverip...etc that will never work should just be text not actual links.

The example setup should be for new recommended setup: All masters. Do not even mention slave servers. This is the setup we use in CA and avoids the need for special xfer issues and complex configuration with multiple views. The only difference is that the crontabs on both NSs are for master jobs. And that the tNSSet has only MASTERs in it.

Another confusing thing in your theory section is where you talk about hardware servers. My initial feeling is that this is wrong see tZone context of one of our zones:

Record Context Info
-------------------
tNSSetMembers w/tNSType:
------------------------
ns1.openisp.net MASTER
ns2.openisp.net MASTER

tNSSetMembers w/tServer:
------------------------
ns1.openisp.net unxsns1.unixservice.com
ns2.openisp.net unxsns2.unixservice.com
#
#iDNS job queue processing
#
#Dual master configuration
* * * * * /usr/sbin/iDNS.cgi ProcessJobQueue ns2.openisp.net >> /var/log/idns-cron.log 2>&1

Changed 3 years ago by Gary

After reviewing (and almost going blind ;) trying to read your screen shots.)

The most important thing to fix ASAP is the NSSet, I thought it was clear that you would use a ns1.smart.com and ns2.smart.com setup. It should be simple and to the point no "theory" needed. Only 2 NSs both masters, do not confuse with multiple master IPs which relates to slave server context. Why? This is what a new user will need to do ASAP to get his system working as against his domain registrar information.

Changed 3 years ago by Hugo

Understood, will update ASAP!

Changed 21 months ago by Dylan

  • status changed from assigned to closed
  • resolution set to wontfix
Note: See TracTickets for help on using tickets.