In my opinion GUIs 'muck it up' too often. A GUI is great when you have a very controlled development environment and the GUI-guy is talking extensively with the Feature-guy. Prime example: Nortel/Bay routers can and usually MUST be managed with SiteManager, a GUI. It is nicknamed SiteMangler, because early version frequently corrupted your router configuration. Later version lacked that feature, but were still broken in some way. Users have demanded and gotten some CLI functions and gotten some in the BCC, but last time I checked, you still can't build a config from scratch using the Nortel CLI. Now do the flipside -- cisco's CLI (command line interface) is straightforward. Like all software, it has bugs, but they are usually quite minor. While the syntax is not the easiest for the initiated, it is fairly consistent. Also speed comes to mind -- at my peak, I could rebuild a Nortel config with ATM/LANE and all the needed bridge groups in 20 minutes. Doing this on a cisco took under 5. Sure there is a learning curve, but the CLI is power! > Hi Mike, > > It is better to learn to do things from the command-line interface. :-) > In what way do you feel Bind 9 is handicapped? > > > On Fri, 8 Nov 2002 tvat3000@netscape.net wrote: > > > I was looking for the GUI way out but I guess I'll suck it up. Thanks for the syntax. This version seems very handicapped. > > > > Mike Starke wrote: > > > > >Hmm, maybe something like: > > > > > >yourdomainname.com. IN MX 0 mail.yourdomainname.com. > > >yourdomainname.com. IN MX 5 mail2.yourdomainname.com. > > > > > >in your Bind files? > > > > > >v/r > > >-Mike > > > > > >On Thu, Nov 07, 2002 at 11:13:51PM -0500, tvat3000@netscape.net wrote: > > >/_How does one set an MX record with RH8?