rdnssd(8) [debian man page]

RDNSSD(8)						      System Manager's Manual							 RDNSSD(8)

NAME

       rdnssd - IPv6 Recursive DNS Server discovery Daemon

SYNOPSIS

       rdnssd [-f] [-H merge-hook] [-r resolv-file] [-p pidfile] [-u username]

DESCRIPTON

       rdnssd  is a daemon program providing client-side support for DNS configuration using the Recursive DNS Server (RDNSS) option, as described
       in RFC 5006.  Its purpose is to supply IPv6 DNS resolvers through stateless autoconfiguration, carried by Router Advertisements.

       rdnssd parses RDNSS options and keeps track of resolvers to write nameservers entries to a resolv.conf(5) configuration file.  By  default,
       it  writes its own separate file, and may call an external hook to merge it with the main /etc/resolv.conf. This is aimed at easing coexis-
       tence with concurrent daemons, especially IPv4 ones, updating /etc/resolv.conf too.

       On Linux, since version 2.6.24, rdnssd takes advantage of a new netlink interface, forwarding RDNSS options  validated  by  the	kernel	to
       userland.  Otherwise, it merely listens to all ICMPv6 traffic through a raw socket.

OPTIONS

       -f or --foreground
	      Do not detach from the console. Run the program in the foreground.

       -H merge-hook or --merge-hook merge-hook
	      Execute this hook whenever resolv.conf is updated. If this option is not specified, then no hook will be called.

       -h or --help
	      Display some help and exit.

       -p pidfile or --pidfile pidfile
	      Override the location of the pidfile.

       -r resolv-file or --resolv-file resolv-file
	      Set the path to the generated resolv.conf file.

       -u username or --user username
	      Override the user that the program will run as. By default, it runs as nobody.

       -V or --version
	      Display program version and license and exit.

FILES

       /etc/rdnssd/merge-hook
	      A basic merge hook shipped with rdnssd, to be called with the -H option.

       /var/run/rdnssd/resolv.conf
	      The default resolv.conf(5) file that rdnssd writes its configuration to.

       /var/run/rdnssd.pid
	      The process-id file.

BUGS

       rdnssd  does  not  keep track of the lifetimes of the routers associated with some DNS resolvers, whereas it should to strictly comply with
       RFC 5006.

       When rdnssd uses a raw socket instead of the netlink kernel interface, it does not validate received Neighbor Discovery traffic in any way.
       For  example,  it  will always consider Router Advertisement packets, whereas it should not if the host is configured as a router. When the
       netlink interface is used, such validation is done by the kernel.

SEE ALSO

       resolv.conf(5), rdisc6(8), ipv6(7)

AUTHOR

       Pierre Ynard <linkfanel at yahoo.fr>

       $Id: rdnssd.8-in 575 2007-12-29 21:55:43Z linkfanel $

       http://www.remlab.net/ndisc6/

rdnssd					       $Date: 2007-12-29 23:55:43 +0200 (Sat, 29 Dec 2007) $					 RDNSSD(8)

Check Out this Related Man Page

COMPAT_ULTRIX(8)					    BSD System Manager's Manual 					  COMPAT_ULTRIX(8)

NAME

     compat_ultrix -- setup procedure for ULTRIX compatibility on MIPS and VAX architectures

DESCRIPTION

     NetBSD/mips and NetBSD/vax architectures can run Risc ULTRIX and VAX ULTRIX executables, respectively.  However, you have to worry about the
     legal issues of ensuring that you have a right to use any ULTRIX binaries on your machine.

     Most executables will work.  The exceptions include programs that use proprietary, ULTRIX-specific features (LAT, CI support, DECnet support)
     and various system calls, ioctl()'s, or ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or buggy (e.g.
     ULTRIX NIS).

     All ULTRIX executables are static, so no shared libraries are required for ULTRIX compatibility.  However, ULTRIX is based on a 4.3BSD alpha
     release.  ULTRIX commands and libraries are often much older than their NetBSD or even SunOS 4.x equivalents, and may require incompatible
     configuration files.

SYSTEM CONFIGURATION FILES

     Set up resolv.conf and svc.conf as below:

	   # mkdir -p /emul/ultrix/etc
	   # cd /emul/ultrix/etc
	   # egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf
	   # cp -p /usr/share/examples/emul/ultrix/etc/*     ./

   /etc/resolv.conf
     The ULTRIX resolver library only understands domain and nameserver lines in resolv.conf(5).  You should create a copy of /etc/resolv.conf
     containing only those commands and put it in /emul/ultrix/etc/resolv.conf.  Note that the domain search order used by ULTRIX executables may
     not be the same as native binaries; there is no good way around this.

   /etc/svc.conf
     ULTRIX uses /etc/svc.conf to select an ordered search of NIS, Hesiod, or local flat-file mappings.  You should create an
     /emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) lookups for all ULTRIX name services.

SEE ALSO

     resolv.conf(5)

BUGS

     RISC ULTRIX NIS (YP) is known to not work.  The ULTRIX NIS libraries have a consistent endian-ness bug.  ULTRIX NIS client will not inter-
     operate with the NetBSD ypbind(8) process.  The only workaround is to use /etc/svc.conf to disable NIS (YP).

     The ndbm hashed-password file used by ULTRIX are incompatible with the db hashed-password file used by NetBSD.  There is no good solution for
     this.  NIS would be a good one, if ULTRIX NIS worked.

     The API used by Xservers to talk to the kernel is currently compatible with ULTRIX 4.1.  An implementation of the ULTRIX 4.2 Xws interface
     (used by X11R6) is in progress.

     A complete list of things which fail to work in ULTRIX compatibility mode should be added here.

BSD
								 January 16, 1999							       BSD

Linux and UNIX Man Pages

rdnssd(8) [debian man page]

Check Out this Related Man Page