Re: bind compatibility from FC2 to FC3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Sa, den 15.01.2005 schrieb mreynolds@xxxxxxxxxxxx um 14:38:

> Since upgrading from FC2 to FC3 my dns does not resolve for my domain
> I am not sure of the exact version on FC 2 but it is 9.2.4-2 on FC 3.

> > It does not work anymore now and from some digging around I noticed 
> > that there are some changes in the named.conf
> > Like the following which was not there before
> The "IN" option was not part of my old conf file ?

> >  zone "testnet" IN {
> >             type master;
> >             file "testnet.zone"

> Micheal Reynolds

rpm -qa | grep bind

I suspect you are running bind-chroot and edit the wrong files:
bind-chroot only sees content below /var/named/chroot/ (that is the
default location).

If above is not the case, then provide exact information like
configuration files and error messages, at least log file entries from
the bind service start.

The IN syntax is optional and proper.

Alexander


-- 
Alexander Dalloz | Enger, Germany | new address - new key: 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora GNU/Linux Core 2 (Tettnang) on Athlon kernel 2.6.10-1.9_FC2smp 
Serendipity 14:47:47 up 22:10, 16 users, 0.20, 0.48, 0.44 

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux