Hello.
First of all..Install the updates,if not You will have a lot of problems!
Josep
Begin of Quote Marvin Suntonvipart :
>Hi all,
>
>
>
>I just recently installed RH9 from RH8 and used the bind config utility to configure
>DNS. On RH8 it was a simple straightforward process and it wor
Hi all,
I just recently installed RH9 from RH8 and used the bind config utility to configure DNS. On RH8 it was a simple straightforward
process and it worked almost instantly.
On RH9 it’s a different story. On the server configuration window the
status is “rndc: connect failed: conn
-i wanted to edit the named.conf through shell but
i dont have the sample.
-is that after i configure name.conf then specify
the file and put it in /var/named/ then is consider
done?
-who have the for LAN forward lookup
and reverse lookup?
assume my lan linux redhad server is
192.168
On Mon, 28 Feb 2000, Cameron Simpson wrote:
> Looks like it coped badly with an ill formed NS record for the 170.210.15.*
> domain (NS records, like MXs, must not point at CNAMEs).
>
> Seems to have restarted happily though. Did it cause any overt problems
> other than the log entries?
No. I wa
On Sun, Feb 27, 2000 at 06:36:31PM -0300, Martin A. Marques wrote:
| The other days I had a problem with named. Restarting named solved the
| problem, but I would like to know why that happened.
[...]
| Feb 25 05:59:25 math named[14902]: "15.210.170.in-addr.arpa IN NS"
| points to a C
| NAME (ultr
The other days I had a problem with named. Restarting named solved the
problem, but I would like to know why that happened.
I'll explain how our name server is working (very good for the past 3
weeks, that was when we installed it). We have a small intranet with
windows and Linux PCs. The server t
