To view MaraDNS in action, do the following:

* Compile MaraDNS. Type in './configure; make' in this directory (the
  top-level MaraDNS directory.)  Note: No need to compile if you
  downloaded a binary RPM or Debian package.

* Install the MaraDNS package. As root:

  	make install

  This will install both the binaries and the man pages for 'maradns',
  'askmara', 'getzone', and 'zoneserver'. In addition, this will (if
  the files are not already present), install an example /etc/mararc,
  make the /etc/maradns directory, and place an example zone file
  (db.example.com) in /etc/maradns. Finally, this will place MaraDNS
  documentation in /usr/local/doc.

* Run the maradns program as root: 

	maradns

  If this does not work, add /usr/local/sbin to your path.  If you are 
  running the Bash shell (the default Linux login shell), the following
  will change you path:

	export PATH=$PATH:/usr/local/sbin/

  In other environments, the procedure for changing you path is different.
  Please read your documentation to get this information. 

  After changing the root directory, binding to UDP port 53, and dropping 
  root privileges, the program will run. Note that the program does not 
  become a daemon.  If you wish to make maradns run as a daemon:

	duende maradns

* In order to change MaraDNS' configuration, please edit the file 
  '/etc/mararc'.  

* To use MaraDNS as a recursive server, copy over
  doc/en/examples/example_recursive_mararc over to /etc/mararc. Next,
  stop (if applicable) then restart maradns

* If MaraDNS is being tested as an recursive nameserver, try one of the
  following:

	dig @127.0.0.3 google.com
	./tools/askmara Agoogle.com. 127.0.0.3

* If MaraDNS is being tested as an authoritative nameserver, test this
  program with one of the following invocations:

	dig @127.0.0.3 example.com
	askmara Aexample.com. 127.0.0.3

Note that this program does not need to run as root if you have
hacked the kernel to allow non-root programs to bind to UDP port 53.
However, when run as a non-root user, the directory is not chrooted,
requiring the paths in the csv1 and csv2 fields to be absolute paths.

Look in doc/en or read the relevant man pages for more information on
how to set up these files.

