The whole process of DNS updates is fully automated.
Certainly, under _normal_ circumstances the problem
should not accure at all and I know all the implications
that would cause. But I know _definitly_ that I want to
use the primary's information ;-)
Deleting the db file would of course be the u
Marcel,
The O'Reilly book on DNS and BIND outlines a way to "roll over" your
serial number on the master and force the slaves to reload. That may be
what you're looking for.
The simplest is, of course, to delete the db file on the slave
server(s), but I'm guessing your probelem is that you don't
Is it possible to force a secondary/slave NS
to do a zone transfer for a particualr zone
_regardless_ of the local stored serial?
I certainly know that this is not recommended
for daily use, but I occasionly have a situation
where this is required.
Any ideas beyond manually deleting the db-file?
3 matches
Mail list logo
