No subject

publically, you aren't actually getting any requests externally. You should
modify your zone that listens on eth0 to reflect your real world IP address.
I have a setup that looks much like this, with the difference that I run my
named's in chroot() jails. You probably don't have to chroot() your name
daemons, but I would definately recommend this as a security feature as well
as a manageability feature.

My guess is that you run one named, with specifying the listen-on directive
to both your IP addresses? If this is the case, then you need to write up
another configuration file and load other zones and set your listen-on
directive to 192.168.1.1 for eth1 and the other named to listen-on
24.whatever. Again, much more manageable if you chroot() them.

Alex

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of spart at jedinights.com
Sent: Wednesday, February 14, 2001 12:15 AM
To: bind-users at isc.org
Subject: Domain not resolving outside network



I've got BIND 9.1 installed on a RH 7.1beta box that's sitting on a 2
machine network.

The box with BIND installed is the gateway, NS, www, and mail server.  It is
setup as the master server for brightloop.com.  dig, whois, and nslookup
queries resolve the domain correctly from inside the network, but it does
not work from outside.

There are no syslog errors and the domain resolves correctly from within the
network so I don't think it is a zone file syntax error.

I tried doing a whois from netsol.com and I got "Domain not found in remote
registrar whois".

I have listen-on 24.43.226.102 (eth0 ip) and 192.168.1.1 (eth1 ip).

I don't know how to diagnose this problem further, and would greatly
appreciate some help.

Thank you,

Ben Bekele