Please help me to understand the following behaviour of Bind 9.7.
Consider this:
NS server1.test.com.
NS server2.test.com.
server1 A 10.0.0.1
server2 A 10.0.0.2
case 1:
# nsupdate
server
On 28/01/11 10:50, Din Jo wrote:
case 1:
# nsupdate
server 127.0.0.1
update delete server2.test.com http://server2.test.com A
update add server2.test.com http://server2.test.com A 10.0.0.2
send
quit
case 2:
# nsupdate
server 127.0.0.1
update delete server2.test.com
In message 4d42a8df.10...@imperial.ac.uk, Phil Mayers writes:
On 28/01/11 10:50, Din Jo wrote:
case 1:
# nsupdate
server 127.0.0.1
update delete server2.test.com http://server2.test.com A
update add server2.test.com http://server2.test.com A 10.0.0.2
send
quit
In case two, you are sending the delete as one transaction and the add
as a 2nd transaction.
I'm surprised the 2nd case fails at the 2nd transaction, not the first.
Known bug. The version information was not passed down to the checking
routines.
Interesting; can you be more specific -
Interesting; can you be more specific - what version info are you
referring to, and which checking routines.
When you update a zone, the new version of the zone has to be internally
consistent. There was a bug where the consistency check was being applied
against the old version of the zone
5 matches
Mail list logo
