listening on different ip addresses
Kevin Darcy
kcd at daimlerchrysler.com
Thu May 2 23:25:51 UTC 2002
Well, 9.1.0 is pretty old. Before you do anything else, upgrade and see if the problem goes away.
- Kevin
Vasiliy Boulytchev wrote:
> Ladies and gents,
> My problem seems extremely simple, yet its driving me absolutely nuts.
> Logs are stating that the server is starting up properly and is listening on all the interfaces (default)
> I take the firewall rules down (to be sure, although its configured properly)
>
> When I do nslookup (from the console)
> server localhost
> yahoo.com
> replies just fine
> server wanip
> yahoo.com
> times out
>
> WHAT THE HECK?
>
> Here's a snapshot of /var/log/messages:
> starting BIND 9.1.0 -u named
> May 2 15:50:02 www named[3817]: using 2 CPUs
> May 2 15:50:02 www named[3819]: loading configuration from '/etc/named.conf'
> May 2 15:50:02 www named: named startup succeeded
> May 2 15:50:02 www named[3819]: the default for the 'auth-nxdomain' option is now 'no'
> May 2 15:50:02 www named[3819]: option 'multiple-cnames' is obsolete
> May 2 15:50:02 www named[3819]: no IPv6 interfaces found
> May 2 15:50:02 www named[3819]: listening on IPv4 interface lo, 127.0.0.1#53
> May 2 15:50:02 www named[3819]: listening on IPv4 interface eth0, wanip#53
> May 2 15:50:02 www named[3819]: listening on IPv4 interface eth1, anothernic#53
> May 2 15:50:03 www named[3819]: running
>
> Here's the top section of my named.conf
>
> options {
> directory "/usr/local/named";
> pid-file "/var/run/named/named.pid";
> transfer-format many-answers;
> notify yes;
> multiple-cnames yes;
> allow-transfer {
> blabla;
> blablabla;
> 127.0.0.1;
> };
> also-notify {
> secondarydnsserverasdfasdf;
> };
> };
>
> zone "." {
> type hint;
> file "/usr/local/named/root.hints";
> };
>
>
> Thanks,
> Vasiliy Boulytchev
> Colorado Information Technologies Inc.
More information about the bind-users
mailing list