-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No worries!
I see you are using port 5353. Be aware of that port number is reserved for Multicast DNS. Best regards, Matthijs Thomas Egrelius wrote: > Hmm... actually this seem to have been a mistake by myself. I wrongly > listed multiple masters inside the <RequestTransfer> statement, while > I should have listed one <RequestTransfer> statement per master. Doing > so seem to have resolved my multiple masters problem ;) > > And the notify listener port.... Using <Port>5353</Port> (upper case > P) instead of <port>5353</port> solved that issue... Sorry for the > confusion. > > /Thomas > > On 27 April 2010 08:03, Matthijs Mekking <[email protected]> wrote: > Hi Thomas, > > We did fix some issues in logging, the zone fetcher logged some wrong > statements. Is this what you are referring to? > > You could see if the zone fetcher picked up the correct set of master > servers. Start the zonefetcher with the option -i. This shows > configuration information and exits. > > Thomas Egrelius wrote: >>>> Hi, >>>> >>>> I have noticed (with 1.0.0) that zone fetcher seem to only accept >>>> notifies from the last one in the list of masters. Notifies from any >>>> of the other masters listed is ignored with the following log message: >>>> >>>> zone_fetcher: [ID 602383 local0.info] zone fetcher refused message >>>> from unauthoritative source: 212.209.15.18 >>>> >>>> If I move the 212.209.15.18 master down to the bottom of the list, the >>>> notify is accepted and acted upon. >>>> >>>> I have also had problems with the Notify listener binding to any other >>>> port than 53, no matter what I enter in the zonefetcher config. >>>> >>>> Is this someting that have been solved in trunk and/or 1.1rc1 already, >>>> or should I open a ticket for it? > It should work. If not, this is bug. Could you provide the zonefetch.xml > file? > > Best regards, > > Matthijs Mekking >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEcBAEBAgAGBQJL1ub7AAoJEA8yVCPsQCW5DssIANNnqe4zx1gDOzvjSc/3k/Ux X/TF3GzpGg2jEBgz2jRBCXgNOciiXkC/+xV2ycwQrPKS2EdAjhL7MG0/ZsbQ2l4a nE48NTtlF37NglA9DzfHlk2FTssRTc0HdWDobnSl9RGu1jKQ36BVXlX0rgZ+dtIc cDz57E0ikPQr9dyZ0ALiVwOnw9QhKJVS37geW5JQPEQ1DNrkJE+AyUxNSOslykd2 Yghn4PXgdWBURQuhzbAfNiS5Aodho2EiFhh9kV0xTwR8qKegVWUpSj+z6G1cSwrm +/4U8hjT5KFwECUXB+f1oFJuIe9hzDSu5gRKISsQI5H0WsptaHDeUhhPW/Rc79w= =4SzA -----END PGP SIGNATURE----- _______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
