fix: increase the DNS allowed response size to solve Data too long for column 'dns_last_result'

[gustavovalverde]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Some DNS servers might reply with several IP addresses. This avoids errors like the following:

Failing: UPDATE `monitor` SET dns_last_result = 'Records: X' WHERE id = 1  - Data too long for column 'dns_last_result' at row 1

Type of change

Please delete any options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

[CommanderStorm]

Some DNS servers might reply with several IP addresses.

Can you provie an entry to reproduce this with?

[CommanderStorm]

you are changing an already existing migration. Please add a new migration instead.
Currently, this does not fix the issue for others due to these lines not gettig applied.

I also don't think that this solves the problem of too large results getting stored. => please truncate what we try to store here instead

[gustavovalverde]

Please add a new migration instead.

This was the first thing I did on my side. Added a file called 2024-07-11-0000-dns-results.js with the following content:

exports.up = function (knex) {
  return knex.schema.table('monitor', function (table) {
    table.string('dns_last_result', 2000).alter();
  });
};

exports.down = function (knex) {
  return knex.schema.table('monitor', function (table) {
    table.string('dns_last_result', 255).alter();
  });
};

But this code did not get executed: https://github.com/louislam/uptime-kuma/blob/master/server/database.js#L393-L396, it seems it just happens when the DB is initialized, not every time the server start (or by a trigger):

uptime-kuma/server/server.js

Line 1671 in 1a5a1a6

await Database.patch();

[gustavovalverde]

FYI @CommanderStorm, the migration issue I'm facing is using mariadb connection type

[gustavovalverde]

Can you provie an entry to reproduce this with?

@CommanderStorm Surely, you can test with mainnet.seeder.zfnd.org