[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Reverse DNS problem after bind upgrade(?)



Hi Nate, 

Don't have any answers for your BIND issue with reverse lookups, but 
you've been kind enough to help me on a couple of things in the past, 
and I wanted to mention that you should probably look into the
"notify" stuff, specifically the "also-notify" statement for named.conf
so your servers stay in sync.  

Your "top" domain server machine sends out a notify message to the other
nameservers whenever a zone file changes and that kickstarts the others
to "come and get it"!  So you just edit in one place, change the serial,
do an ndc reload [zone], and as fast as your machines can do zone
transfers to each other, all of them are updated... very useful
feature in BIND 8.

The TTL values still are in effect for the rest of the Internet, but
at least internally your changes are done.

We currently have six machines set up this way at work, and even the
other five nastly little NT machines ... (GRIN) ... are participating
in the fun.  If I change something in the main machine, it gets pushed
almost instantly to the rest of the organization, nationwide.  Very
nice stuff.

On Mon, Dec 27, 1999 at 12:17:19PM -0800, aphro wrote:
> i just added the $TTL value last night so maybe its possible that the
> other servers just havent updated ? I am running bind 8.2.2p5-0slink.  i
> believe my DNS is working since it works when i query it directly..

-- 
Nate Duehr <nate@natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.

Attachment: pgpUoLSQh7wmN.pgp
Description: PGP signature


Reply to: