Re: SOA RNAME Value

2011-04-18 Thread Justin Krejci
I do not understand why I did not get similar test and log results as you indicate below but I appreciate your feedback! Thank you!! On Thu, 2011-04-14 at 17:39 +0100, Tony Finch wrote: > Justin Krejci wrote: > > > > So I am wondering if this is normal/expected behavior for BIND and if so > > sh

Re: SOA RNAME Value

2011-04-14 Thread Tony Finch
Justin Krejci wrote: > > So I am wondering if this is normal/expected behavior for BIND and if so > should debug logging or named-checkzone with debugging be able to > identify this as the problem. Or am I missing something else altogether? With bind-9.7.3, I get the following log messages with t

Re: SOA RNAME Value

2011-04-14 Thread Justin Krejci
Sorry, was a long day (for other reasons) here is a maybe an easier to follow summary. When the SOA RNAME value does not include the final dot at the end you append the zone automatically. The zone in this case contains a forward slash character "/" which is not a valid email addr

SOA RNAME Value

2011-04-13 Thread Justin Krejci
Hello List, When troubleshooting a particular reverse delegated zone to us we used the normal "d/26.c.b.a.in-addr.arpa" naming for the zone. A couple of zones did not get served correctly (tried on BIND 9.7.0-P2 and 9.7.3) and any query for a record within these zones always came back with a SERVF