Oli

unfortunately, I can't help you as I no longer have a makerbot printer. Most likely the protocol has changed since this repository has had its last update 7 years ago....

I do like the suggestion. With the newly introduced EDE support we can get some feedback on resolution issues from resolvers that support it, but a full traversal check within...

My suggestion for the fix would be two things: * Handle "413 Payload Too Large" gracefully, i.e. show error message ("Too large for submission") * Maybe increase the limit a...

yeah, there are quite a few :) - I've already started to the reduce the node count as there are admittedly several places where he walls don't have to follow...

no worries, the nginx limit actually forced me to optimize, so it ain't that bad ;-) - after removing tons of unnecessary nodes the submission was successful. I guess handling...

"no keys/signatures in the registry + zone is signed" is called an "island of security". This is pretty common. People want to test signing their zones first without causing any...

also, it should configurable per zone if the zone is supposed to be an island of security or not. in case the DS gets removed without the zone administrators knowledge...

looks like mullvad is interfering with the detection of the default resolver. Querying a specific resolver / auth server works fine through mullvad.