[bind] adding forwarding for 1 zone destroys MX records for all other zones

[Kevin Darcy]

Can you resolve any *non*-MX records for the Internet?

Here's my theory as to what's happening:

1) Your Internet name resolution has broken somehow
2) When you query an Internet MX record, it therefore fails
3) upon failure, nslookup silently appends your default domain (or uses a searchlist, if
one is configured). So it looks up, e.g. bigfoot.com.sonydnse.com
4) There is a wildcard MX in sonydnse.com which matches that.


- Kevin

Nico De Ranter wrote:

> Howdy,
>
> I have a curious problem: I added forwarding for one specific zone through
> our Intranet, stopped bind, cleared the cache and restarted again:
>
> zone "sonydnse.com" {
>       type forward;
>       forwarders { 43.194.154.4; };
> };
>
> (Note: running bind 8.2.3).  Now when I do "nslookup -type=MX sonydnse.com"
> I get ofcourse the MX record for our intranet. When I do the same thing for
> another .com-domain afterwards (e.g. "nslookup -type=MX bigfoot.com") I get
> the MX records from my intranet in stead of the MX records from the Internet.
> If I do a query for the MX record of a non-existing .com-domain, e.g. feglkjsdgkl.com
> I get exactly the same result (instead of a non-existing domain message).
> .org domains have no problem.
>
> If I remove the zon "sonydnse.com" part again and clean the cache the problsm disapear.
>
> Any ideas?
>
> Nico
>
> ---------------------------------------------------------
>  "It has been said that there are only two businesses that
>   refer to customers as users: illegal drug trade and
>                the computer industry."
> ---------------------------------------------------------
> Nico De Ranter
> Sony Service Center (SDCE/NEE-B)
> Sint Stevens Woluwestraat 55 (Rue de Woluwe-Saint-Etienne)
> 1130 Brussel (Bruxelles), Belgium, Europe, Earth
> Telephone: +32 2 724 86 41 Telefax: +32 2 726 26 86
> e-mail: nico.deranter at sonycom.com