Re: BIND to listen on all interfaces?
On Wed, Jul 04, 2007 at 03:14:28PM +1000, Mikhail Goriachev wrote: Nejc Škoberne wrote: Hello, I am running BIND (from base system) on my FreeBSD 5.3 machine. The box is connected to outer world via ADSL connection (tun0 device). If the named is started when the machine is connected to the internet, then everything is OK, I get this by saying netstat -n -a: udp4 0 0 X.X.X.X.53 *.* udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* but at boot time, the named starts before the PPP connection is started, so the tun0 interface is not up yet. So that's why I get this: udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* In BIND manual, it says: If no listen-on is specified, the server will listen on port 53 on all interfaces. I also tried to specify the ADSL IP address in named.conf (it is static), but it is still a no go. I don't have such problems with other daemons! Any ideas? An idea: Assuming you're using ppp, let it restart named after it connects to the Internet. Have a /etc/ppp/ppp.linkup and put the following or similar into it: adsl: ! /etc/rc.d/named restart Read the ppp man pages for further details. Regards, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: www.webanoide.org Another option can be the use of interface-interval: interface-interval The server will scan the network interface list every interface-interval minutes. The default is 60 minutes. The maximum value is 28 days (40320 minutes). If set to 0, interface scanning will only occur when the configuration file is loaded. After the scan, the server will begin listening for queries on any newly discovered interfaces (provided they are allowed by the listen-on configuration), and will stop listening on interfaces that have gone away. (from BIND ARM). HTH, Yuri pgp8CM2KmWqHH.pgp Description: PGP signature
Re: BIND to listen on all interfaces?
On Tue, Jul 03, 2007, Nejc Škoberne wrote: I also tried to specify the ADSL IP address in named.conf (it is static), but it is still a no go. I don't have such problems with other daemons! Any ideas? Is the interface already up when you are starting BIND? I guess it is not. I haven't tested myself but you might try to add the very same IP you use for your ADSL interface as an alias to the lo0 device. This way the IP is available all the time, thus BIND should be able to listen on it. While it might look strange to have to same IP on two different interfaces (lo0 and ADSL in your case) IIRC it should work flawlessly. Just give it a try and report back if it works or not. -cs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
BIND to listen on all interfaces?
Hello, I am running BIND (from base system) on my FreeBSD 5.3 machine. The box is connected to outer world via ADSL connection (tun0 device). If the named is started when the machine is connected to the internet, then everything is OK, I get this by saying netstat -n -a: udp4 0 0 X.X.X.X.53 *.* udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* but at boot time, the named starts before the PPP connection is started, so the tun0 interface is not up yet. So that's why I get this: udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* In BIND manual, it says: If no listen-on is specified, the server will listen on port 53 on all interfaces. I also tried to specify the ADSL IP address in named.conf (it is static), but it is still a no go. I don't have such problems with other daemons! Any ideas? Thanks, Nejc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND to listen on all interfaces?
Nejc Škoberne wrote: Hello, I am running BIND (from base system) on my FreeBSD 5.3 machine. The box is connected to outer world via ADSL connection (tun0 device). If the named is started when the machine is connected to the internet, then everything is OK, I get this by saying netstat -n -a: udp4 0 0 X.X.X.X.53 *.* udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* but at boot time, the named starts before the PPP connection is started, so the tun0 interface is not up yet. So that's why I get this: udp4 0 0 127.0.0.1.53 *.* udp4 0 0 10.0.1.3.53*.* In BIND manual, it says: If no listen-on is specified, the server will listen on port 53 on all interfaces. I also tried to specify the ADSL IP address in named.conf (it is static), but it is still a no go. I don't have such problems with other daemons! Any ideas? An idea: Assuming you're using ppp, let it restart named after it connects to the Internet. Have a /etc/ppp/ppp.linkup and put the following or similar into it: adsl: ! /etc/rc.d/named restart Read the ppp man pages for further details. Regards, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: www.webanoide.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
