Problem with .fr domains [TEST check if server is really recursive]: answer refused from server (IN/SOA: fr.)

[Sam Trenholme]

>Now it works :) But only with configure --authonly ; make

Not to be rude, but works for me.  This is a standard build of MaraDNS
1.3.14 with recursive support:

---

maradns &
[1] 6750
$ THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

To not display this message, add the follwing to your mararc file:

hide_disclaimer = "YES"

Using default ICANN root servers
 Log: Root directory changed
 Log: Binding to address 127.0.0.4
 Log: Socket opened on UDP port 53
 Log: Root privileges dropped
Processing zone domain.com. right now.
Filename: db.domain.com
MaraDNS proudly serves you 10 DNS records
MaraDNS maximum memory allocation set to 1613249536 bytes
 Log: All RRs have been loaded

$ askmara Adomain.com. 127.0.0.4
# Querying the server with the IP 127.0.0.4
# Question: Adomain.com.
domain.com. +3600 a 10.1.2.3
# NS replies:
domain.com. +3600 ns ns1.nameserver.com.
domain.com. +3600 ns ns3.nameserver.com.
domain.com. +3600 ns ns2.nameserver.com.
# AR replies:
$ askmara -v Adomain.com. 127.0.0.4 | grep avail
Recurs available: 1
$ kill %1
[1]+  Terminado               maradns
$ grep -v recursive_acl /etc/mararc > foo
$ mv foo /etc/mararc
$ maradns &
[1] 6769
$ THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

To not display this message, add the follwing to your mararc file:

hide_disclaimer = "YES"

 Log: Root directory changed
 Log: Binding to address 127.0.0.4
 Log: Socket opened on UDP port 53
 Log: Root privileges dropped
Processing zone domain.com. right now.
Filename: db.domain.com
MaraDNS proudly serves you 10 DNS records
MaraDNS maximum memory allocation set to 2636800 bytes
 Log: All RRs have been loaded

$ askmara -v Adomain.com. 127.0.0.4 | grep avail
Recurs available: 0
$ maradns --version
This is MaraDNS version 1.3.14
Compiled on a Linux system at mar ago 4 17:52:41 CDT 2009
For usage information, 'man maradns'

---

Marcus, at this point, I've fixed the bug and you're doing something wrong.
I've taken responsibility for fixing the bug MaraDNS had.

As long as you use MaraDNS 1.3.14, and don't have recursion enabled (in
other words, "grep -v recursive_acl /etc/mararc > foo ; mv foo /etc/mararc"
[1]), MaraDNS, as you can see above, has RA set to zero for queries.

This is, to be blunt, a problem between chair and keyboard (PBCAK) issue and
I don't resolve those without being paid.  I'm closing this ticket.  The bug
has been fixed.

I'm not going to teach you how to use nano to find and remove all, not just
some, but all references to "recursive_acl" in your mararc file, or how to
delete all copies of older releases of MaraDNS from your path, or whatever
it is that is causing your problem.  Not unless you start paying me for my
time.

All of this discussion has uncovered a bug MaraDNS had, but the bug has been
fixed at this point.  Just do the "./configure --authonly ; make" thing; it
fixes the problem for you.

Thanks for your understanding.  Please talk to another UNIX system
administrator; don't waste everyone's time on the list with any more
discussion about this issue.

- Sam

[1] If you can't read this but of UNIX scripting, don't do this; it's a
little dangerous.