From nobody@FreeBSD.org  Mon Mar 20 08:15:36 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B2A0A16A423
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Mar 2006 08:15:36 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 40CD943D53
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Mar 2006 08:15:36 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k2K8FZrA077681
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 20 Mar 2006 08:15:35 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k2K8FZnH077680;
	Mon, 20 Mar 2006 08:15:35 GMT
	(envelope-from nobody)
Message-Id: <200603200815.k2K8FZnH077680@www.freebsd.org>
Date: Mon, 20 Mar 2006 08:15:35 GMT
From: "Pavel E. Petrov" <kamenka@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: BIND9-named strange behavior
X-Send-Pr-Version: www-2.3

>Number:         94721
>Category:       ports
>Synopsis:       BIND9-named strange behavior
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    dougb
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 20 08:20:18 GMT 2006
>Closed-Date:    Thu May 18 05:09:37 GMT 2006
>Last-Modified:  Thu May 18 05:09:37 GMT 2006
>Originator:     Pavel E. Petrov
>Release:        6.1-prerelease
>Organization:
"TD Polimerstroymaterialy", LTD
>Environment:
FreeBSD tdpsm.spb.ru 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #1: Sat Mar 18 15:37:44 MSK 2006     admin@tdpsm.spb.ru:/usr/obj/usr/src/sys/RAINBOW-II  i386
>Description:
After upgrading from 5.3-release to 6.1-prerelease i found that system stop
to make resolvings. There was found an ipfw rule which drops packets to
local named daemon. It was antispoofing rule. So there is a problem:

vr0 is an interface with ip 192.168.1.201
bind listens at 192.168.1.201:53

When i try to do any resolving, system sends packets at 192.168.1.201:53
through lo0, so ipfw antispoof rule drops it coz of missinterfacing.

netstat -rn shows stright pass for all 192.168.1 subnet : LINK#2 (which is vr0)

Now i just skip this rule and all works well.

Note, that 5.3 with its older bind9 was OK with it. The problem started
exactly after upgrading kernel and world.
>How-To-Repeat:
I havent any thoughts.
>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->dougb 
Responsible-Changed-By: edwin 
Responsible-Changed-When: Mon Mar 20 08:24:27 UTC 2006 
Responsible-Changed-Why:  
Over to maintainer 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94721 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Tue Mar 21 07:36:53 UTC 2006 
State-Changed-Why:  
Does this apply to bind in the base system, or the one installed from ports? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94721 
State-Changed-From-To: feedback->closed 
State-Changed-By: dougb 
State-Changed-When: Thu May 18 05:08:32 UTC 2006 
State-Changed-Why:  

Feedback timeout. 

Also, this looks like a combination of bad named.conf options, 
bad firewall rules, or both. If this is still a problem for 
you, I would suggest sending a message to freebsd-questions@ 
with more information about both of those. 

Good luck, 

Doug 

http://www.freebsd.org/cgi/query-pr.cgi?pr=94721 
>Unformatted:
