Some time ago people here may remember that Dave or Kent (twiddle dee dum
and twiddle dee doo) said that the new bind9 DNS server would not support
alternate root zones. This concerned me as I had heard rumour some months
earlier - probably generated by twiddle dee or twiddle do - that the same
was the case. At the time a few people were to investigate - but I never
heard back.
Anyway - the the ORSC has run tests on bind 9 - specifically release
9.0.0rc4. Our tests show that bind9 runs alternate roots without any
problem whatsoever. I have attached supporting data to this message which
proves the same. Well also keep an eye on this. I'll be asking Henry our
admin who did the tests if he would not mind keeping an eye on bind9 -
just in case.
Once again twiddle dee dum and twiddle dee doo are trying to fuck us with
gibberish. I don't approciate the time and confonded confusion these
twist cause. They are senior respected programmers in their own rights
and the fools are a discredit to every professional - it just plain
dishonest FUD.
I want to thank Henry from quasar.net who was kind enought to volunteer
his time in running test. It's very much appreciated - three cheers for
Henry.
For the record here is the output.
>From [EMAIL PROTECTED] Sat Aug 26 18:51:22 2000
Date: Sat, 26 Aug 2000 18:42:49 -0400 (EDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Bind9
Nope, no errors. This is all I get from syslog when starting the named:
Aug 26 18:31:58 chipclip named[31431]: starting BIND 9.0.0rc4
Aug 26 18:31:58 chipclip named[31434]: loading configuration from
'/etc/named.conf'
Aug 26 18:31:58 chipclip named[31434]: no IPv6 interfaces found
Aug 26 18:31:58 chipclip named[31434]: listening on IPv4 interface lo,
127.0.0.1#53
Aug 26 18:31:58 chipclip named[31434]: listening on IPv4 interface eth0,
208.243.146.130#53
Aug 26 18:31:58 chipclip named[31434]: listening on IPv4 interface eth1,
208.5.42.193#53
Aug 26 18:31:58 chipclip named[31434]: listening on IPv4 interface eth1:0,
192.168.10.1#53
Aug 26 18:32:00 chipclip named[31434]: running
And here is the zone from named.conf:
zone "." {
type hint;
file "db.root";
};
I always tail the syslog for a few minutes after a restart...make sure
nothing kooky happens.
--Henry
On Sat, 26 Aug 2000, Simon Higgs wrote:
> At 12:03 AM 8/26/00 -0400, [EMAIL PROTECTED] wrote:
>
> Is there now an error in the log that looks like this:
>
> [Date] [Time] [Host] named: /etc/named.conf:[line#]: cannot redefine zone
> '.' class IN
>
> >It still works.
> >
> >--Henry
> >
> >On Fri, 25 Aug 2000, Simon Higgs wrote:
> >
> > > At 05:20 PM 8/24/00 -0400, [EMAIL PROTECTED] wrote:
> > >
> > > What happens if you add the hints file for just the ORSC root servers:
> > >
> > > zone "." {
> > > type hints;
> > > file "named.ca";
> > > };
Joe Baptista
http://www.dot.god/
dot.GOD Hostmaster
+1 (805) 753-8697
