No subject


Tue Apr 2 00:56:56 UTC 2013


H.ROOT-SERVERS.NET.     5d15h54m22s IN A  128.63.2.53
C.ROOT-SERVERS.NET.     5d15h54m22s IN A  192.33.4.12
G.ROOT-SERVERS.NET.     5d15h54m22s IN A  192.112.36.4
F.ROOT-SERVERS.NET.     5d15h54m22s IN A  192.5.5.241
B.ROOT-SERVERS.NET.     5d15h54m22s IN A  128.9.0.107
J.ROOT-SERVERS.NET.     5d15h54m22s IN A  198.41.0.10
K.ROOT-SERVERS.NET.     5d15h54m22s IN A  193.0.14.129
L.ROOT-SERVERS.NET.     5d15h54m22s IN A  198.32.64.12
M.ROOT-SERVERS.NET.     5d15h54m22s IN A  202.12.27.33
I.ROOT-SERVERS.NET.     5d15h54m22s IN A  192.36.148.17
E.ROOT-SERVERS.NET.     5d15h54m22s IN A  192.203.230.10
D.ROOT-SERVERS.NET.     5d15h54m22s IN A  128.8.10.90
A.ROOT-SERVERS.NET.     5d15h54m22s IN A  198.41.0.4

There is no real need to set a cron job to update this file often.  It 
does not change much and BIND only uses the hints file at startup to ask 
one of them for the current listing.  After that it ignores the contents 
of your hints file. 

Mike

--
Mike Ashcraft, Sr. Network Engineer
epixtech, Inc.
M.Ashcraft at epixtech.com





"Jason Williams" <hizzow at cfl.rr.com>
Sent by: bind-users-bounce at isc.org
10/09/00 08:03 PM

 
        To:     <bind-users at isc.org>
        cc: 
        Subject:        Auto Root Zone Updates?


I recently setup a BIND 8 Server, I setup the server using the DNS HOWTO
that is included in the LDP (Linux Documentaion Project).  Towards the end
of the HOWTO, there is a script that uses Dig to get the latest Zone info
from internic.  My problem is this, I'm getting timeouts from Internic. 
The
script runs fine, my connectivity is fine, so i'm assuming that Internic 
has
shut off that type service (why I don't know)  Is there another way to
Automaticly update the root Zone file without going through the FTP 
server?



Below is the Script that i was using,  Respective Rights to the author of
the script.


Thanks,
Jason Williams



#!/bin/sh
#
# Update the nameserver cache information file once per month.
# This is run automatically by a cron entry.
#
# Original by Al Longyear
# Updated for bind 8 by Nicolai Langfeldt
# Miscelanious error-conditions reported by David A. Ranch
# Ping test suggested by Martin Foster
#
(
 echo "To: hostmaster <hostmaster>"
 echo "From: system <root>"
 echo "Subject: Automatic update of the root.hints file"
 echo

 PATH=/sbin:/usr/sbin:/bin:/usr/bin:
 export PATH
 cd /var/named

 # Are we online?  Ping a server at your ISP
 case `ping -qnc some.machine.net` in
   *'100% packet loss'*)
        echo "The network is DOWN. root.hints NOT updated"
        echo
        exit 0
        ;;
 esac

 dig @rs.internic.net . ns >root.hints.new 2>&1

 case `cat root.hints.new` in
   *NOERROR*)
        # It worked
        :;;
   *)
        echo "The root.hints file update has FAILED."
        echo "This is the dig output reported:"
        echo
        cat root.hints.new
        exit 0
        ;;
 esac

 echo "The root.hints file has been updated to contain the following
information:"
 echo
 cat root.hints.new

 chown root.root root.hints.new
 chmod 444 root.hints.new
 rm -f root.hints.old
 mv root.hints root.hints.old
 mv root.hints.new root.hints
 ndc restart
 echo
 echo "The nameserver has been restarted to ensure that the update is
complete."
 echo "The previous root.hints file is now called
/var/named/root.hints.old."
) 2>&1 | /usr/lib/sendmail -t
exit 0









More information about the bind-users mailing list