Florian Weimer wrote:
> * Martin Schulze:
>
> > Disabled again. The problem lies somewhere "between" saens and you.
> > It's fine on saens locally.
>
> While the bogus A record should be gone now that saens is down, you
> should still remove saens from the list of authoritative name servers
> fo
* Martin Schulze:
> Disabled again. The problem lies somewhere "between" saens and you.
> It's fine on saens locally.
While the bogus A record should be gone now that saens is down, you
should still remove saens from the list of authoritative name servers
for debian.{org,com,net} and ipv6.debian
Neil McGovern wrote:
> I'm forwarding this over to debian-admin, as they're the people who can
> fix this :)
I had already answered Bjoern:
Ah yes, the named on saens went alive again. That was not planned.
Disabled again. The problem lies somewhere "between" saens and you.
It's fine on saens
I'm forwarding this over to debian-admin, as they're the people who can
fix this :)
Neil
On Mon, May 29, 2006 at 10:57:06AM +0200, Bjørn Mork wrote:
> First, not so serious, but still an error: All debian.org servers have
> a mismatch between the delegation and the served data, adding
> samosa.de
First, not so serious, but still an error: All debian.org servers have
a mismatch between the delegation and the served data, adding
samosa.debian.org as autoritative (I know samosa is listed as primary
in the SOA record, but it need not, and should not, be listed as
autoritative as long as it's no
5 matches
Mail list logo
