Please help with these DNS hiccups

[Barry Margolin]

In article <cbv232$23l4$1 at sf1.isc.org>,
 "Andrew" <fakeaddress at lan.com.nl> wrote:

> Hello There,
> 
> I seem to be slowly getting things happening but I have to pain you with
> some questions.
> My resolv.conf file has the following
> 
> domain eziekiel.com
> search eziekiel.com
> nameserver 127.0.0.1 listening
> nameserver 192.168.0.2  (DNS server) listening

I've never seen "listening" in the resolv.conf file.  Is that really in 
the file, or is it just commentary by you for the post?

> With only this in it I can not ping a host name through Firewall gateway on
> 192.168.0.1 but as soon as I add
> 192.168.0.1 which is the internal interface of my firewall & is also
> assigned
> DNS servers of my DSL provider it starts working. Also say I do a dig . If I
> remove 192.168.0.1 & just leave my DNS IP's (127.0.0.1 & 192.168..0.2) it
> hangs & comes back with
> dig mx bmw.com
> ; <<>> DiG 9.2.1 <<>> mx bmw.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
> & i get status: SERVFAIL,
> 
> Can you give me an educated guess on why ( I just don't know why it would be
> the firewall that is the culprit) because I have allowed internal network
> through as "any" & if you check my domain name "eziekiel.com" externally
> through online DNS checking tools all seems fine. I mean when the checking
> pages checks for config options of my internal machine it hits firewall with
> request on port 53 & then this is forwarded to nominated 192. system which
> then returns relevant info.

You probably need to configure your nameserver to forward to 
192.168.0.1, i.e.

options {
  ...
  forwarders { 192.168.0.1; };
};

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***