[ISC-Bugs #926] (bind9) BIND9.1.1rc3 not compatible with rc2

Systems systems at buzzcity.com
Fri Mar 2 08:11:04 UTC 2001


Hi Andrews,

Guess you're tackling whale of problems in making things
better for all the BIND users. I think you will be glad
to know part of the reason for my difficulty in putting
rc3 to work with rc2.

To give rc3 one more chance, I run server D (rc3) to
load zones from server B (rc2). Server D consistently
refuse to load all reverse zones from server B. The
reason for the transfer error is that all the reverse
zonesfile (db.xxx.xxx.xxx) on server B (rc2) use
"include" for another separate file containing the
same SOA record for all the reverse zones.

Now, server D (rc3) load the zone files db.xxx.xxx.xxx
without the SOA record, hence the transfer error messages.

Now, it up to you to debug (gdb) why rc2 can load the
whole reverse zone file from rc2, but not rc3 from rc2.

Thanks

-----Original Message-----
From: Tan Yang Kwang <yktan at buzzcity.com>
To: Mark.Andrews at nominum.com <Mark.Andrews at nominum.com>
Date: Wednesday, February 28, 2001 2:25 PM
Subject: Re: [ISC-Bugs #926] (bind9) BIND9.1.1rc3 not compatible with rc2


>-----Original Message-----
>From: Mark.Andrews at nominum.com <Mark.Andrews at nominum.com>
>To: Tan Yang Kwang <yktan at buzzcity.com>
>Cc: Mark.Andrews at nominum.com <Mark.Andrews at nominum.com>
>Date: Wednesday, February 28, 2001 11:36 AM
>Subject: Re: [ISC-Bugs #926] (bind9) BIND9.1.1rc3 not compatible with rc2
>
>
>>
>>> Hi, I'm the sort who like to keep things simple. While
>>> it is still fresh in my mind, will just go along with
>>> your "interrogation"... ;-p
>>>
>>> -----Original Message-----
>>> From: Mark.Andrews at nominum.com <Mark.Andrews at nominum.com>
>>> To: Tan Yang Kwang <yktan at buzzcity.com>
>>> Cc: Request Tracker <bind9-bugs at isc.org>
>>> Date: Wednesday, February 28, 2001 10:46 AM
>>> Subject: Re: [ISC-Bugs #926] (bind9) BIND9.1.1rc3 not compatible with
rc2
>>>
>>> >
>>> >>
>>> >> Okay.. try to be more concise..
>>> >>
>>> >> 1. successfully compile rc3, say on server A.
>>> >> 2. Server A's named.conf configured for rc2
>>> >>    has been working for a few days in rc2 (server A)
>>> >> 3. Run rc3 on server A, but zone transfer fails
>>> >>    using server A's old named.conf, server A act as
>>> >>    secondary to server B
>>> >
>>> > What was logged during this run?  Both on server A and server B.
>>> > Also which OS?
>>> >
>>>
>>> Server B's /var/adm/messages just contain error messages about
>>> zone transfers being denied by server B.
>>
>> I presume this was server A's log?
>
>Affirmative.
>
>>> Server B logging in /var/adm/messages is similar.
>>
>> Why were they denied?  Was the client address wrong?
>> Does server A have transfer-source defined?
>
>
>Don't know. Server B (rc2) reject transfer with
>server A (rc3) but not Server A (rc2). Named.conf
>on server B and A have not been changed.
>
>>
>>> In addition, another server C
>>> trying to load from server A was denied too, with the error
>>>  messages of "refresh callback refused", probably because
>>> TTLs on server A ran out.
>>>
>>> Server A when running rc3 do not have any error messages or
>>> coredump or any logging whatsoever. Named just exit silently.
>>>
>>> Only one OS, i.e. SunOS 5.x
>>>
>>> >> 4. quickly restore server A back to rc2 and server A works again
>>> >> 5. transfer rc3's binaries from server A to server B
>>> >> 6. try to run rc3 on server B, named refuse to stay resident
>>> >>    with about 4 or more attempts
>>> >
>>> > What was logged?
>>> > Was there a core dump?
>>> >
>>>
>>> None, that I can recall. When I was just starting out with rc2 a few
>>> weeks back, I came across the file /usr/named/core which is a big
>>> file. However, there is no core in rc3 for both server A and B.
>>
>> If named dropped core it will be in the directory specfied
>> by the directory option.  Could you send us a stack backtrace?
>>
>> e.g.
>> gdb named /usr/named/core
>
>Sorry... /usr/named/core is already deleted. Command "gdb" not
>found.
>
>>>
>>> >> 7. give up running rc3 on server B, restore server B back to rc2
>>> >> 8. check that now both server A and server B doing zone transfer,
>>> >>    no more error messages in /var/adm/messages
>>> >> 9. no more testing, promised (boss not amused!)
>>> >>
>>> >> NB: Both server A and B running the same UNIX OS and same platform.
>>> >> FYI. working copies of rc2's binaries is generated on server A and
>>> >> is used by all other servers as well as server B.
>>> >>
>>> >> Regards.
>>> >>
>>--
>>Mark Andrews, Nominum Inc.
>>1 Seymour St., Dundas Valley, NSW 2117, Australia
>>PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com
>>
>Thank you, Tan YK




More information about the bind-users mailing list