Can we somehow not do that?
A solution would need to a) not lose important debug info, b) not fail to recover from network issues and c) not hard fail if libpagekite starts up before the networking subsystem.
This may actually be caused by oversized DNS responses and embedded resolver limitations. Making sure the records don't get too large at the server side might also help.
Can we somehow not do that?
A solution would need to a) not lose important debug info, b) not fail to recover from network issues and c) not hard fail if libpagekite starts up before the networking subsystem.
This may actually be caused by oversized DNS responses and embedded resolver limitations. Making sure the records don't get too large at the server side might also help.