Hi,
i have tested the avahi-dnsconfd daemon.
With this entries in my avahi-daemon.conf:
[server]
#host-name=foo
domain-name=local
browse-domains=clausklein.homelinux.net
use-ipv4=yes
[wide-area]
enable-wide-area=yes
[publish]
publish-workstation=yes
publish-domain=yes
publish-dns-servers=192.168.1.2
publish-resolv-conf-dns-servers=yes
#########################
Is started the daemon:
P3linux:/usr/local/etc # tail -26 /var/log/messages | grep avahi
Apr 1 15:53:16 P3linux avahi-daemon[23678]: avahi-daemon 0.6.9 starting up.
Apr 1 15:53:16 P3linux avahi-daemon[23678]: Successfully called chroot().
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Successfully dropped remaining
capabilities.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Loading service file
/services/http.service.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Loading service file
/services/monit.service.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Loading service file
/services/snmp.service.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Loading service file
/services/ssh.service.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Failed to create IPv6 socket,
proceeding in IPv4 only mode
Apr 1 13:53:16 P3linux avahi-daemon[23678]: New relevant interface eth1.IPv4
for mDNS.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Joining mDNS multicast group on
interface eth1.IPv4 with address 192.168.2.3.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: New relevant interface eth0.IPv4
for mDNS.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.3.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Network interface enumeration
completed.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Registering new address record for
192.168.2.3 on eth1.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Registering new address record for
192.168.1.3 on eth0.
Apr 1 13:53:16 P3linux avahi-daemon[23678]: Registering HINFO record with
values 'I686'/'LINUX'.
Apr 1 13:53:17 P3linux avahi-daemon[23678]: Server startup complete. Host name
is P3linux.local. Local service cookie is 4290943280.
Apr 1 13:53:18 P3linux avahi-daemon[23678]: Service "Remote Terminal on
P3linux" (/services/ssh.service) successfully established.
Apr 1 13:53:18 P3linux avahi-daemon[23678]: Service "SNMP server on P3linux"
(/services/snmp.service) successfully established.
Apr 1 13:53:18 P3linux avahi-daemon[23678]: Service "Monit server on P3linux"
(/services/monit.service) successfully established.
Apr 1 13:53:18 P3linux avahi-daemon[23678]: Service "Web server on P3linux"
(/services/http.service) successfully established.
Apr 1 15:53:31 P3linux avahi-dnsconfd[23694]: Successfully connected to Avahi
daemon.
Apr 1 15:53:31 P3linux avahi-dnsconfd[23694]: New DNS Server 192.168.1.1
(interface: 3.IPv4)
Apr 1 15:53:31 P3linux avahi-dnsconfd[23694]: New DNS Server 192.168.1.2
(interface: 3.IPv4)
Apr 1 15:53:31 P3linux avahi-dnsconfd[23694]: New DNS Server 192.168.1.1
(interface: 2.IPv4)
Apr 1 15:53:31 P3linux avahi-dnsconfd[23694]: New DNS Server 192.168.1.2
(interface: 2.IPv4)
P3linux:/usr/local/etc #
# my resolv.conf looks like that:
P3linux:/usr/local/etc # cat /etc/resolv.conf
nameserver 192.168.1.2
nameserver 192.168.1.1
nameserver 192.168.1.2
nameserver 192.168.1.1
P3linux:/usr/local/etc #
My first question is : Why is there no search enttry?
Second why are there double entries, my name server is only available over one
interface?
Perhaps, should there be too a damain name entry?
From man RESOLV.CONF(5)
domain Local domain name.
Most queries for names within this domain can use short names
relative to the local domain. If no domain entry is present, the domain is
determined from the local host name returned by gethostname();
the domain part is taken to be everything after the first `.'. Finally, if
the host name does not contain a domain part, the root domain is
assumed.
search Search list for host-name lookup.
The search list is normally determined from the local domain
name; by default, it contains only the local domain name. This may be
changed by listing the desired domain search path following the
search keyword with spaces or tabs separating the names. Resolver queries
having fewer than ndots dots (default is 1) in them will be
attempted using each component of the search path in turn until a match is
found. For environments with multiple subdomains please read
options ndots:n below to avoid man-in-the-middle attacks and unnecessary
traffic for the root-dns-servers. Note that this process may be
slow and will generate a lot of network traffic if the servers for the
listed domains are not local, and that queries will time out if
no server is available for one of the domains.
claus klein
_______________________________________________
avahi mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/avahi
