Si vous avez créé une configuration analogue à celle décrite ci-dessus,
vous pouvez lancer les commandes d'initialisation de bind.
Ces commandes (avec leur alternative entre parenthèses) sont:
/etc/rc.d/init.d/named start
( /etc/init.d/named start ) ( /etc/init.d/bind start ) /etc/rc.d/init.d/named stop /etc/rc.d/init.d/named restart /etc/rc.d/init.d/named status |
Jul 8 15:45:23 ns1 named[17656]: status. named
8.2.2-P5 sat Aug 5 13:21:24 DET 2000 ^I
Jul 8 15:45:23 ns1 named[17656]: hint zone ``'' (IN) loaded (serial 0) Jul 8 15:45:23 ns1 named[17656]: master zone ``localhost'' (IN) loaded (serial 2000012101) Jul 8 15:45:23 ns1 named[17656]: master zone ``1.0.0.127.in-addr.arpa'' (IN) loaded (serial Jul 8 15:45:23 ns1 named[17656]: master zone ``cranzgot.co.za'' (IN) loaded (serial 20000121 Jul 8 15:45:23 ns1 named[17656]: master zone ``myisp.co.za'' (IN- loaded (serial 20^0012101 Jul 8 15:45:23 ns1 named[17656]: master zone ``2.168.192.in-addr.arpa'' (IN) loaded (serial Jul 8 15:45:23 ns1 named[17656]: master zone ``144.28.196.in-addr.arpa'' (IN) loaded (serial Jul 8 15:45:23 ns1 named[17656]: master zone ``44.181.123.160.in-addr.arpa'' (IN) loaded (se Jul 8 15:45:23 ns1 named[17656]: listening on [127.0.0.1].53 (lo) Jul 8 15:45:23 ns1 named[17656]: listening on [196.28.144.16].53 (eth0) Jul 8 15:45:23 ns1 named[17656]: Forwarding source address is [0.0.0.0].1041 Jul 8 15:45:23 ns1 named: named startup succeeded Jul 8 15:45:23 ns1 named[17657]: group = 25 Jul 8 15:45:23 ns1 named[17657]: user = named Jul 8 15:45:23 ns1 named[17657]: Ready to answer queries. |