From Newsgroup: alt.privacy.anon-server

Only one remailer meets distance etc...

Not one yamer over 99%.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 2/17/26 05:58, Nomen Nescio wrote:

Only one remailer meets distance etc...

Not one yamer over 99%.

It looks like Zax's mixmin.net server is having name resolution issues.
This affects some pingers and remailers but not others.

Also it is affecting the Mixmin Yamn pinger. Which other Yamn remailers
may rely on for their own functionality.
--
SEC3

My PGP key:
<https://keys.openpgp.org/vks/v1/by-keyid/C94D423355A83863>
--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 17 Feb 2026, SEC3 <admin@sec3.net> posted some news:189513d85b146270$353080$4044784$802601b3@news.usenetexpress.com:

On 2/17/26 05:58, Nomen Nescio wrote:

Only one remailer meets distance etc...

Not one yamer over 99%.

It looks like Zax's mixmin.net server is having name resolution issues.
This affects some pingers and remailers but not others.

Depends which DNS servers are queried, how, and from where. Host lookups failing mostly.

Lookup by hostname fleegle.mixmin.net

nslookup fleegle.mixmin.net 208.67.222.222
Server: dns.sse.cisco.com
Address: 208.67.222.222

DNS request timed out.
timeout was 2 seconds.
*** Request to dns.sse.cisco.com timed-out


Reverse lookup using the ipv4 address.

nslookup 144.76.182.167 208.67.222.222
Server: dns.sse.cisco.com
Address: 208.67.222.222

Name: fleegle.mixmin.net
Address: 144.76.182.167

nslookup 144.76.182.167 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Name: fleegle.mixmin.net
Address: 144.76.182.167

IPV6

nslookup 2a01:4f8:200:60a6::2 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Name: fleegle.mixmin.net
Address: 2a01:4f8:200:60a6::2

whois

canonical name fleegle.mixmin.net.
aliases
addresses 144.76.182.167

His DNS servers are all up and responding - but one was missing from the
usual lot earlier.

whois mixmin.net

Updated Date: 2025-11-27T09:48:40Z
Creation Date: 2005-11-26T13:58:30Z
Registry Expiry Date: 2026-11-26T13:58:30Z

Name Server: NS3.CYPHERPUNKS.EU
Name Server: NS4.MUSTELID.NET
Name Server: BINGO.MIXMIN.NET
Name Server: FLEEGLE.MIXMIN.NET

nslookup fleegle.mixmin.net www.mixmin.net
Server: UnKnown
Address: 144.76.182.167

Name: fleegle.mixmin.net
Addresses: 2a01:4f8:200:60a6::2
144.76.182.167

Also it is affecting the Mixmin Yamn pinger. Which other Yamn remailers
may rely on for their own functionality.

Definitely some DNS changes occurring.

These are the DNS servers from an earlier query.

Name Server: NS3.CYPHERPUNKS.EU
Name Server: NS4.MUSTELID.NET
Name Server: BINGO.MIXMIN.NET
Name Server: FLEEGLE.MIXMIN.NET

Checking today.

Name Server: ATOMANT.MIXMIN.NET <-
Name Server: BINGO.MIXMIN.NET
Name Server: FLEEGLE.MIXMIN.NET
Name Server: NS3.CYPHERPUNKS.EU
Name Server: NS4.MUSTELID.NET

10 minutes later - all gone.

DNS query for snorky.mixmin.net returned an error from the server: ServerFailure

DNS query for mixmin.net returned an error from the server: ServerFailure

No records to display

I run my own DNS servers using various forwarders. No problems here for mixmin name resolution - yet.

FWIW, his web and mail servers are still up and running.
A couple of other things I know he's involved with are up and running, no
need to mention them here.

Defintely some changes going on.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Jack Ryan wrote:

Defintely some changes going on.

It's dying iron ;) !

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Depends which DNS servers are queried, how, and from where. Host lookups failing mostly.

The DNSSEC signatures on the records expired. https://dnsviz.net/d/mixmin.net/dnssec/

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 18 Feb 2026, Nomen Nescio <nobody@dizum.com> posted some news:20260218233709.8A1pb6P4j618@sewer.dizum.com:

Depends which DNS servers are queried, how, and from where. Host
lookups failing mostly.

The DNSSEC signatures on the records expired. https://dnsviz.net/d/mixmin.net/dnssec/

Admin usually gets an email about that. Also server time drift or
automatic resigning failed.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 18 Feb 2026, Nomen Nescio <nobody@dizum.com> posted some news:20260218233709.8A1pb6P4j618@sewer.dizum.com:

Depends which DNS servers are queried, how, and from where. Host
lookups failing mostly.

The DNSSEC signatures on the records expired. https://dnsviz.net/d/mixmin.net/dnssec/

A DNSSEC operation on his domain didn't successfully complete, and DNSSEC
key sets were left in place, eventually getting expired.

He probably didn't get the email.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 18 Feb 2026, Jack Ryan <noreply@remailer.cpunk.us> posted some news:e3ec9c563e0ad865d790d2e7edda1512@dizum.com:

On 18 Feb 2026, Nomen Nescio <nobody@dizum.com> posted some news:20260218233709.8A1pb6P4j618@sewer.dizum.com:

Depends which DNS servers are queried, how, and from where. Host
lookups failing mostly.

The DNSSEC signatures on the records expired.
https://dnsviz.net/d/mixmin.net/dnssec/

A DNSSEC operation on his domain didn't successfully complete, and
DNSSEC key sets were left in place, eventually getting expired.

He probably didn't get the email.

mixmin.net is resolving again.

all dns records present and healthy.

It's just a matter of everything catching up again.

--- Synchronet 3.21b-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 18 Feb 2026, Jack Ryan <noreply@remailer.cpunk.us> posted some news:35d172ae2731273c9e747cf437f4c93c@dizum.com:

On 17 Feb 2026, SEC3 <admin@sec3.net> posted some news:189513d85b146270$353080$4044784$802601b3@news.usenetexpress.com:

On 2/17/26 05:58, Nomen Nescio wrote:

Only one remailer meets distance etc...

Not one yamer over 99%.

It looks like Zax's mixmin.net server is having name resolution
issues. This affects some pingers and remailers but not others.

Depends which DNS servers are queried, how, and from where. Host
lookups failing mostly.

No great loss since neodome is censoring everything anyway.
--- Synchronet 3.21b-Linux NewsLink 1.2