intranet machines name problem

[Kevin Darcy]

Later versions of BIND tend to be more strict about what they accept. Chances
are you have something "illegal" in your zonefiles that used to work, but now
causes the zone to not load properly. I can only guess at what this
"illegality" might be, since you have only posted "sample" zonefiles...


- Kevin

Marcelo Telles wrote:

> Hi.
> I have the following problem. When I upgraded my bind (using apt-get on a
> debian), some of the machines of my network stoped working... I really
> don't know what is happening.
> Here is an example:
>
> Let's suppose my domain is myprovider.net and it's IP is 200.200.200.1.
> then my /var/named/named.myprovider.net looks like this one:
>
> dns1            IN      A       200.200.200.1
> www             IN      CNAME   dns1
> ftp             IN      CNAME   dns1
> proxy           IN      CNAME   dns1
> dns             IN      CNAME   dns1
> radio           IN      CNAME   dns1
> ultra           IN      CNAME   dns1
>
> I can ping www.myprovider.org, but can't ftp.myprovider.org....
>
> And if i have another domain called otherdomain.net, and it's on a a
> machine with the ip 200.200.200.2, it's /var/named/named.otherdomain.net
> should look like this:
>
> $ORIGIN otherdomain.net.
>
> @               IN      SOA     dns1.myprovider.net.
> info.myprovider.com.br. (
>                 10068200001 3600 600 86400 3600 )
>                 IN      NS      dns1.myprovider.net.
>                 IN      MX      10 dns2.myprovider.net.
>
> www             IN      A       200.200.200.2
>
> But i *doesn't* work.....
>
> All this configs where working fine until I tried to update bind....
>
> Thank you for any help
> Marcelo
>
> ----
> linux *is* user friendly... It's just selective about who its friends are.