named appears to be ignoring incoming requests

[Kevin Darcy]

You don't have a "blackhole" option defined, by any chance?


- Kevin

dave wrote:

> I'm a bind newbie and I've run into a problem I can't find an answer to
> anywhere. I'm in the process of switching my servers to a new subnet,
> and currently my ISP is giving me access to both the new and old
> subnets on the same wire.
>
> I've set up Bind 9.1.3 on one of my Linux boxes, with the new subnet on
> a second NIC (eth1). The name server (ns1.covecomm.com) seems to work
> fine locally - I can see it responding to DNS requests from 127.0.0.1.
> But I'm unable to get it to respond to any requests from elsewhere,
> i.e. I've tried from one of my old subnet addresses, even with
> firewalls down on both machines, and I only get the following:
>
> # dig @ns1.covecomm.com a
>
> ; <<>> DiG 8.2 <<>> @ns1.covecomm.com a
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; res_nsend to server ns1.covecomm.com  139.142.208.177: Connection
> timed out
>
> netstat confirms that named is in fact listening on 53 on that
> addressl; tcpdump confirms that a DNS request does in fact arrive at
> the interface to which the address is bound; allow-query is set to any.
> But named never responds to the request. I've gone to level 10
> debugging and I never see any response in the log to that packet coming
> in.
>
> Any help appreciated.
>
> Dave
> dave at covecomm.com