The glue issue wouldn’t affect it. That’s you’re using nameservers with *.com tlds for a *.net domain for example. technacally that’s against the rules but pretty much ignored now a days.

If the draft is being save instantly, I’m leaning towards outbound pings myself as the issue. The ping plugin that you link to wouldn’t affect it since all it does it appears is not resend pings. The pings still go out when you publish. That plugin just doesn;t try resending them if you’ve published the post in the past.

There’s a different ping plugin but I can’t find it right off. It sends pings out later on when it has time instead of all at once.

Here’s some extra info:
<brag> and probably a real solution </brag>:
it turns out, that function spawn_cron() in cron.php takes a timeout of 5 minutes, at least at Nedlinux. My website is hosted at Nedlinux and I’m quite happy with them, but this is an undesired effect.

As a solution, which works for me, I patched cron.php, line 87:
– $argyle = @ fsockopen( $parts[‘host’], $_SERVER[‘SERVER_PORT’], $errno, $errstr, 0.01 );
+ $argyle = @ fsockopen( $parts[‘scheme’].’://’.$parts[‘host’], $_SERVER[‘SERVER_PORT’], $errno, $errstr, 0.01 );

The original call tried to open http://www.duinkerken.nu:80, the patched version tries to open http://www.duinkerken.nu:80

…and now I can finally start blogging… 🙂