bind problem solved, sort of

Cecil H. Whitley cwhitley at ec.rr.com
Sun May 5 23:14:17 EDT 2002


Hi again,
I actually have definitive answers this time (got skipjack loaded so I can
use nslookup).  The actual commands:

server servername.dom # Sets nslookup to query a specific server

set type=soa # sets nslookup to query only soa information.

I know dig and host are the "new" tools but i'm from the old school and as
long as I have nslookup source that's what i'll use!  The soa record
provides the serial number of the table from which the server is answering.
By querying the secondary dns's soa for your domain you will get the serial
number which should match the serial number in your primary tables.  For
example I use the four digit year, the two digit month, the two digit day
and then a two digit counter for the day.  That gives me a serial number
like 2002050501.  So, the actual commands are:

bash$ nslookup
> server backup.mydomain.dom # substitute actual name
> set type=soa
> mydomain.dhs.org
The resulting information should match the @soa record's information on your
primary dns.  Typically it should not take more than an hour to "catch up".

Sorry about the bad syntax in my previous post.

Regards,

Cecil





More information about the Speakup mailing list