After my primary (and only) internal nameserver blew
a power supply yesterday, I am now motivated enough
to bring on a secondary nameserver for internal use.

My primary is running on a Debian box and I have had
no problems geting them all (internal & external) configured.
I have an openBSD box running dhcp & squid, and I just thought
it would be easier to lump on bind services as well.

I have it configured to the point where bind starts
'named -b /var/named/named.boot -t /var/named'
and doing a 'nslookup' locally works as well. The
file '/var/named/namedb/mydomain.bak' has been transfered
over, and all appears well locally.

Here is the problem: WHen I set my /etc/resolv.conf on my notebook
(another debain install :-) to have this new server as my first
nameserver, it chokes. It is not answering queries.

I did a 'netstat -lan | grep 53' on the new nameserver, and it appears
as if it is only listening on tcp port, not udp. 

Did I miss something somewhere? Any tips?

v/r
Mike
Did