Avahi has a problem with bind9 db.local-file and the localzone in named.conf
I reported this bug at bugs.debian.org -- with the solution.
Maybe for someone who has the same problem
Greetings
Erik
----- Original Message -----
From: Erik Grootjans
To: submit@bugs.debian.org
Sent: Sunday, November 15, 2009 8:47 PM
Subject: Avahi has a problem with bind9 db.local-file and the localzone in
named.conf
Package: Bind9
Version: 1:9.5.1.dfsg.P3-1
I have made a default installation of bind and are using it for resolving my
networknames.
Everytime i started a fresh installed computer, i did get an icon with :
avahi is disabled because your using a .local network....
I did. So I did re-install a few computers, and on the other computers i
changed /etc/hosts /etc/resolv.conf and /etc/network/interfaces. Futher i
looked at al configuration programs for .local.
I checked this 3 times.
With the dns server off -- i had no messages from avahi.
but with the dns server on -- i got the messages and the disabling of avahi
I did a test (found it on avahi.org):
host -t SOA local.
and did get the next answer:
local has SOA record localhost. root.localhost 2604800 86400 2419200
604800.
I did recognize this as the db.local file from bind9
which is used to define localhost
I did a rename from db.local to db.localhost and changed
in named.conf zone local to zone localhost and db.local in db.localhost
I did again:
host -t SOA local.
and did get the next respons:
host local. not found (3NXDOMAIN)
--> so avahi will NOT disable itsself... (hallelujah!!!)
I waited by the computer after a restart. And saw avahi come on, but didnot
get any messages off disabeling avahi.
I looked at the logs nothing. So this is a solution.
Why is this is this a bug ????
Is there a way to get bind9 and avahi work together, using the default
installation names/files. This are default packages!!!
Why do i have to change db.local in db.localhost
There is something NOT compatable with the names of the files in the
pacakages !!!
But it works now !!!!
I'm using debian 5.00 with the latest versionss
of avahi 0.6.23
of bind 1:9.5.1.dfsg.P3-1
----- Original Message -----
From: "Avahi" <trac-noreply@tango.0pointer.de>
Cc: <avahi-tickets@mail.0pointer.de>
Sent: Sunday, November 15, 2009 5:23 PM
Subject: Re: [Avahi] #291: Avahi has a problem with bind9 db.local-file and
the localzone in named.conf
#291: Avahi has a problem with bind9 db.local-file and the localzone in
named.conf
-----------------------------+----------------------------------------------
Reporter: Erik | Owner: lennart
Type: defect | Status: closed
Milestone: | Component: avahi-core
Resolution: distrospecific | Keywords:
-----------------------------+----------------------------------------------
Changes (by lennart):
* status: new => closed
* resolution: => distrospecific
Comment:
That script which checks for the .local SOA is a downstream addition of
Debian's, which I however think makes a lot of sense. Nonetheless please
bring this up downstream, i.e. in the Debian BTS, since it is a downstream
bug.
If you ask me shipping a db.local in bind9 is really a bda idea.
--
Ticket URL: <http://avahi.org/ticket/291#comment:1>
Avahi <http://avahi.org/>
The Avahi mDNS/DNS-SD Engine
===
#291: Avahi has a problem with bind9 db.local-file and the localzone in
named.conf
--------------------+-------------------------------------------------------
Reporter: Erik | Owner: lennart
Type: defect | Status: new
Milestone: | Component: avahi-core
Keywords: |
--------------------+-------------------------------------------------------
I did use a .local network
I did 3 client re-installs of the debian system
on 2 other systems i changed /etc/hosts /etc/resolv.conf
/etc/network/interfaces
At the last 2 systems i looked at al the conf files from later installed
packages, if there was a reference to my old domainname.
(I looked in sendmail, bind, apache, ftp,hylafax and dhcp3 and found
several and corrected them)
I did not look once but even tree times
Some times at startup i did get an error from the avahi-daemon.
Sometimes the avahi warning icon.
I looked at your website and found
a script with a test.
I did the test:
host -t SOA local.
and did get the next answer:
local has SOA record localhost. root.localhost 2604800 86400 2419200
604800.
I did recognize this as the db.local file from bind9
which is used to define localhost
I did a rename from db.local to db.localhost and changed
in named.conf zone local to zone localhost and db.local in db.localhost
I did again:
host -t SOA local.
and did get the next respons:
host local. not found (3NXDOMAIN)
--> so avahi will NOT disable itsself... (hallelujah!!!)
Why is this is this a bug ????
Is there a way to get bind9 and avahi work together, using the default
installation names/files.
Why do i have to change db.local in db.localhost
I'm using debian 5.00 with avahi 0.6.23
--
Ticket URL: <http://avahi.org/ticket/291>
Avahi <http://avahi.org/>
The Avahi mDNS/DNS-SD Engine
Reply to: