Its working. Did you happen to /just/ fix it?

-bash-2.05b$ dig @ns1.bos.ma.meganet.net. ci.malden.ma.us NS

; <<>> DiG 9.2.3 <<>> @ns1.bos.ma.meganet.net. ci.malden.ma.us NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3348
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;ci.malden.ma.us. IN NS

;; ANSWER SECTION:
ci.malden.ma.us. 86400 IN NS reuben.meganet.net.
ci.malden.ma.us. 86400 IN NS ns1.bos.ma.meganet.net.
ci.malden.ma.us. 86400 IN NS ns1.prv.ri.meganet.net.

;; ADDITIONAL SECTION:
ns1.bos.ma.meganet.net. 86400 IN A 209.213.72.9
ns1.prv.ri.meganet.net. 86400 IN A 209.213.80.9
reuben.meganet.net. 86400 IN A 209.213.64.2

;; Query time: 41 msec
;; SERVER: 209.213.72.9#53(ns1.bos.ma.meganet.net.)
;; WHEN: Thu Dec 9 12:16:57 2004
;; MSG SIZE rcvd: 163

-----Original Message-----
From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org]On
Behalf Of Paul A
Sent: Thursday, December 09, 2004 11:54 AM
To: bind-users@isc.org
Subject: Non-authoritative problem


I have a domain ci.malden.ma.us which I need to be authoritative for in
order for the us nic to point the dns server to me.

My dns server are=20

Reuben.meganet.net
Ns1.bos.ma.meganet.net
Ns1.prv.ri.meganet.net

I have created a primary zone in reuben and entered them as secondary in
ns1.bos and ns1.prv. The zones get transferred from reuben to ns1.prv =
and
ns1.bos with no problem. The only problem is when I do a dig on =
ns1.bos.ma I
get a non-authoritative answer. For reuben and ns1.prv.ri its working =
fine.
I used rndc to flush and reload dns, I updated the serial and nothing on
ns1.bos.ma. the named.conf file is the same on ns1.prv.ri (working) as =
it is
on ns1.bos.ma, not working.

Any ideas.

Thanks,
=20
----------------------------------------------------
Paul Amaral
MegaNet Communications
P: 508 646 0030
-----------------------------------------------------

> -----Original Message-----
> From: bind-users-bounce@isc.org [mailto:bind-users-bounce@isc.org] On
> Behalf Of Uwe Gansert
> Sent: Thursday, December 09, 2004 7:59 AM
> To: bind-users@isc.org
> Subject: Re: nss_lwres and lwresd problem
>=20
> On Wednesday 01 December 2004 15:30, Uwe Gansert wrote:
>=20
> > I'm not able to make nss_lwres and lwresd work together.
> > I've installed bind 9.3.0 and nss_lwres 0.93 on an i586 system. =

In=3D3D20
> > my /etc/nsswitch.conf I have=3D3D20
> > hosts: files lwres dns

>=20
> BTW, in the meantime I found out that it helps to delete the
> /etc/lwresd.co=3D
> nf=3D20
> file. I did not manage to configure a working version of =

/etc/lwresd.conf
> b=3D
> ut=3D20
> it seems to work with the built in defaults.
> Is there some kind of magic in that file? Mine looked like this:
>=20
> options {
> pid-file "/var/run/named/lwres.pid";
> allow-query { any; };
> allow-recursion { any; };
> listen-on port 921 { 127.0.0.1; };
> };
>=20
> logging {
> channel default_debug {
> file "/var/run/named/named.run";
> severity dynamic;
> };
> category default {default_syslog; default_debug; };
> };
>=20
> and starting lwresd shows no problems in the log file and it's =

listening
> on=3D
> =3D20
> 953 and 921.
>=20
> =3D2D-=3D20
> ciao, Uwe Gansert
>=20
> Uwe Gansert, Server Technologies Team
> SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 N=3DFCrnberg, =

Germany
> e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0,
> =3D46ax: +49-(0)911-74053-476, Web: http://www.suse.de =3D20