Sophie: pdns-3.0.1-0.1mdv2010.2 i586

pdns-3.0.1-0.1mdv2010.2.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Testing your install</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="PowerDNS manual"
HREF="index.html"><LINK
REL="UP"
TITLE="Installing on Unix"
HREF="installing-on-unix.html"><LINK
REL="PREVIOUS"
TITLE="Installing on Unix"
HREF="installing-on-unix.html"><LINK
REL="NEXT"
TITLE="Running PDNS on unix"
HREF="pdns-on-unix.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PowerDNS manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="installing-on-unix.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Installing on Unix</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="pdns-on-unix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="TESTING"
>2.2. Testing your install</A
></H1
><P
>	After installing, it is a good idea to test the basic functionality of the software before configuring database backends.
	For this purpose, PowerDNS contains the 'bindbackend' which has a domain built in example.com, which is
	officially reserved for testing.

	To test, edit <TT
CLASS="FILENAME"
>pdns.conf</TT
> and add the following if not already present:
	
	<PRE
CLASS="SCREEN"
>	  launch=bind
	  bind-example-zones
	</PRE
>

	<DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>	    As of 2.9.21, the BIND backend no longer features the 'bind-example-zones' command. These will return in 2.9.22.
	  </P
></TD
></TR
></TABLE
></DIV
>

	This configures powerdns to 'launch' the bindbackend, and enable the example zones. To fire up PDNS in testing mode, execute: 
	<B
CLASS="COMMAND"
>/etc/init.d/pdns monitor</B
>, where you may have to substitute the location of your SysV init.d location you 
	specified earlier.

	In monitor mode, the pdns process runs in the foreground and is very verbose, which is perfect for testing your install.
	
	If everything went all right, you can query the example.com domain like this:
	<PRE
CLASS="SCREEN"
>	  <B
CLASS="COMMAND"
>host www.example.com 127.0.0.1</B
>
	</PRE
>
	www.example.com should now have IP address 1.2.3.4. The <B
CLASS="COMMAND"
>host</B
> command can usually be found in the dnsutils 
	package of your operating system. Alternate command is: <B
CLASS="COMMAND"
>dig www.example.com A @127.0.0.1</B
> or even 
	<B
CLASS="COMMAND"
>nslookup www.example.com 127.0.0.1</B
>, although nslookup is not advised for DNS diagnostics.

	<P
></P
><UL
><LI
><P
>	      example.com SOA record
	    </P
></LI
><LI
><P
>	      example.com NS record pointing to ns1.example.com
	    </P
></LI
><LI
><P
>	      example.com NS record pointing to ns2.example.com
	    </P
></LI
><LI
><P
>	      example.com MX record pointing to mail.example.com
	    </P
></LI
><LI
><P
>	      example.com MX record pointing to mail1.example.com
	    </P
></LI
><LI
><P
>	      mail.example.com A record pointing to 4.3.2.1
	    </P
></LI
><LI
><P
>	      mail1.example.com A record pointing to 5.4.3.2
	    </P
></LI
><LI
><P
>	      ns1.example.com A record pointing to 4.3.2.1
	    </P
></LI
><LI
><P
>	      ns2.example.com A record pointing to 5.4.3.2
	    </P
></LI
><LI
><P
>	      host-0 to host-9999.example.com A record pointing to 2.3.4.5
	    </P
></LI
></UL
>

	When satisfied that basic functionality is there, type <B
CLASS="COMMAND"
>QUIT</B
> to exit the monitor mode. 
	The adventurous may also type <B
CLASS="COMMAND"
>SHOW *</B
> to see some internal statistics. 

	In case of problems, you will want to read the following section.
      </P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2674"
>2.2.1. Typical errors</A
></H2
><P
>	  At this point some things may have gone wrong. Typical errors include:
	  <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
><SPAN
CLASS="ERRORTYPE"
>binding to UDP socket: Address already in use</SPAN
></DT
><DD
><P
>		  This means that another nameserver is listening on port 53 already. You can resolve this problem
		  by determining if it is safe to shutdown the nameserver already present, and doing so. If uncertain,
		  it is also possible to run PDNS on another port. To do so, add <B
CLASS="COMMAND"
>local-port=5300</B
> to
		  <TT
CLASS="FILENAME"
>pdns.conf</TT
>, and try again. This however implies that you can only test your nameserver
		  as clients expect the nameserver to live on port 53.
		</P
></DD
><DT
><SPAN
CLASS="ERRORTYPE"
>binding to UDP socket: Permission denied</SPAN
></DT
><DD
><P
>		  You must be superuser in order to be able to bind to port 53. If this is not a possibility,
		  it is also possible to run PDNS on another port. To do so, add <B
CLASS="COMMAND"
>local-port=5300</B
> to
		  <TT
CLASS="FILENAME"
>pdns.conf</TT
>, and try again. This however implies that you can only test your nameserver
		  as clients expect the nameserver to live on port 53.
		</P
></DD
><DT
><SPAN
CLASS="ERRORTYPE"
>Unable to launch, no backends configured for querying</SPAN
></DT
><DD
><P
>		  PDNS did not find the <B
CLASS="COMMAND"
>launch=bind</B
> instruction in pdns.conf.
		</P
></DD
><DT
><SPAN
CLASS="ERRORTYPE"
>Multiple IP addresses on your server, PDNS sending out answers on the wrong one</SPAN
>, <SPAN
CLASS="ERRORTYPE"
>Massive amounts of 'recvfrom gave error, ignoring: Connection refused'</SPAN
></DT
><DD
><P
>		  If you have multiple IP addresses on the internet on one machine, UNIX often sends out answers over another interface
		  than which the packet came in on. In such cases, use <B
CLASS="COMMAND"
>local-address</B
> to bind to specific IP addresses, which
		  can be comma separated. The second error comes from remotes disregarding answers to questions it didn't ask to that IP address
		  and sending back ICMP errors.
		</P
></DD
></DL
></DIV
>
	</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="installing-on-unix.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="pdns-on-unix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Installing on Unix</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installing-on-unix.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Running PDNS on unix</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>