bind9 and microsoft issues

[Adam Majer <adamm@galacticasoftware.com>]

Hi all,

I keep getting flooded with messages like

Jan 31 17:30:14 polaris named[232]: client 207.46.150.12#32645: query (cache) denied
Jan 31 17:30:14 polaris named[231]: client 207.46.150.12#32645: query (cache) denied
Jan 31 17:30:14 polaris named[232]: client 207.46.150.12#32645: query (cache) denied
Jan 31 17:30:14 polaris named[231]: client 207.46.150.12#32645: query (cache) denied
Jan 31 17:30:14 polaris named[232]: client 207.46.150.12#32645: query (cache) denied
Jan 31 17:48:01 polaris named[231]: client 207.46.245.10#2567: query (cache) denied
Jan 31 17:48:01 polaris named[232]: client 207.46.245.10#2567: query (cache) denied
Jan 31 17:48:01 polaris named[231]: client 207.46.245.10#2567: query (cache) denied
Jan 31 17:48:01 polaris named[232]: client 207.46.245.10#2567: query (cache) denied

but these only occur from those IP ranges... Now traceroute and host do not
resolve these but whois says this is part of MICROSOFT-GLOBAL-NET (207.46.0.0).

I allow query for everyone for the domains that are to be public

zone "zombino.com"{
        type master;
        file "db_my_domain";
        allow-transfer{
          {some IPs here}
        };
        allow-query { any; };
};

Is this a bind9 issue (woody) or MS has their computers screwed up?

I can only reproduce it if I try to use my server as a DNS for a domain
that query is not allowed [like `host umanitoba.ca zombino.com`].

Thanks,
- Adam