This is true but very inconvenient if you happen to have a dynamic ip.
(case in point, myself =] ) and the bind op guide says you should prefer
0.0.0.0 over 127.0.0.1 if you are going to use a local alias.

If not responding to a request to 0.0.0.0 was intentional this is news to
me.  When I brought this up before (see pr #5645 and mail archives
"0.0.0.0 Weirdness") I was told this should be supported. 

Maybe we can put this one to rest before 1.4?

On Mon, 17 Aug 1998, Simon J. Gerraty wrote:

> 
> >In message <199808162356.TAA10460@Twig.Rodents.Montreal.QC.CA>, der Mouse write
> >s:
> >>This is not really a change to resolv.conf.  It's a change to the
> >>networking code, so that 0.0.0.0 is no longer interpreted as "this
> 
> >But I guess it makes sense, and it's not hard to adapt to, once you know
> >about it.
> 
> IIRCC using 0.0.0.0 or 127.0.0.1 can cause you to lose when your nameserver
> forwards a query - it lists that address as the original requester and the
> remote nameserver sends the answer to himself.
> 
> Using the IP addr of your box's main net interface is much safer.
> 
> --sjg
>