Patrik Kernstock
9aad2926fb
INWX: Fix INWX provider after their unexpected data-type breaking-change ( #3855 )
...
Fixes #3854
Unfortunately I couldn't run the integrationTests properly as INWX
doesn't seem to have properly updated their sandbox environment (it
still presents `int` instead of `string` like production). Hence, the
tests do fail. I don't want to run this against my own production
account, to be frank.
See:
```shell
$ curl -X POST https://api.ote.domrobot.com/xmlrpc/ -H "Content-Type: application/xml" -d '<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
<methodName>nameserver.info</methodName>
<params>
<param>
<value>
<struct>
<member>
<name>user</name>
<value>
<string>[USER]</string>
</value>
</member>
<member>
<name>lang</name>
<value>
<string>en</string>
</value>
</member>
<member>
<name>pass</name>
<value>
<string>[PASS]</string>
</value>
</member>
<member>
<name>domain</name>
<value>
<string>[DOMAIN]</string>
</value>
</member>
</struct>
</value>
</param>
</params>
</methodCall>' | xmllint --format - | grep -iE "id|roId" -C3
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3968 0 2971 100 997 13375 4488 --:--:-- --:--:-- --:--:-- 17954
<value>
<struct>
<member>
<name>roId</name>
<value>
<int>9677</int>
</value>
--
<value>
<struct>
<member>
<name>id</name>
<value>
<int>118057</int>
</value>
--
<value>
<struct>
<member>
<name>id</name>
<value>
<int>118060</int>
</value>
--
<value>
<struct>
<member>
<name>id</name>
<value>
<int>79610</int>
</value>
--
<value>
<struct>
<member>
<name>id</name>
<value>
<int>77243</int>
</value>
--
</value>
</member>
<member>
<name>svTRID</name>
<value>
<string>20251127--ote</string>
</value>
```
Hence, only done manualy tests via `dnscontrol push --domains
<example.com>`:
(tested create, delete and modify)
```text
CONCURRENTLY checking for 0 zone(s)
SERIALLY checking for 1 zone(s)
Serially checking for zone: "example.tld"
CONCURRENTLY gathering records of 0 zone(s)
SERIALLY gathering records of 1 zone(s)
Serially Gathering: "example.tld"
******************** Domain: example.tld
3 corrections (PK-INWX)
#1 : - DELETE _test1.example.tld TXT "123" ttl=43200
SUCCESS!
#2 : ± MODIFY _test2.example.tld TXT ("1234" ttl=43200) -> ("12345" ttl=43200)
SUCCESS!
#3 : + CREATE _test4.example.tld TXT "123" ttl=43200
SUCCESS!
Done. 3 corrections.
```
2025-11-29 12:17:13 -05:00
Tom Limoncelli
89c65b6683
INWX: Permit "." target for SRV records ( #3377 )
2025-01-16 10:03:00 -05:00
Gert Van Gool
cd371c1149
INWX: support MxNull records ( #2700 )
...
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
2023-12-08 11:58:24 -05:00
nemunaire
5ae231030e
Update version in go.mod ( #2382 )
2023-05-20 13:21:45 -04:00
Patrik Kernstock
1ef7c80e3a
INWX: Enabling TXT with 255 bytes works ( #2380 )
2023-05-20 13:19:15 -04:00
Tom Limoncelli
61e500b7dc
DEV: Optimize integration tests ( #1742 )
2022-09-07 14:08:06 -04:00
Tom Limoncelli
31723ad146
PERFORMANCE: Refactor auditrecords.go to loop only once #1570 ( #1658 )
...
* stash
* Use rejectif idea
* rename
* wip!
* Convert old systems to new
* fixup!
* fix typo
2022-08-11 17:24:47 -04:00
Tom Limoncelli
959f721c04
MAINT: Update TXT docs, suggest not using TxtNoLen255 ( #1548 )
...
* suggest not using TxtNoLen255
* Rename functions
* wip!
* fixing!
2022-06-20 11:34:05 -04:00
Tom Limoncelli
8dea9edc34
Re-engineer TXT records for simplicity and better compliance ( #1063 )
...
TXT records are now handled different.
1. The raw input from dnsconfig.js is passed all the way to the provider. The provider can determine if it can or can't handle such records (auditrecords.go) and processes them internally as such.
2. The CanUseTXTMulti capability is no longer needed.
* DSPs now register a table of functions
* Use audits for txt record variations
* unit tests pass. integration fails.
* fix deepcopy problem
* rename to AuditRecordSupport
* Reduce use of TXTMulti
* Remove CanUseTXTMulti
* fix Test Skip
* fix DO
* fix vultr
* fix NDC
* msdns fixes
* Fix powerdns and cloudflare
* HEDNS: Fix usage of target field to resolve TXT handling (#1067 )
* Fix HEXONET
Co-authored-by: Robert Blenkinsopp <robert@blenkinsopp.net>
Co-authored-by: Jakob Ackermann <das7pad@outlook.com>
2021-03-07 13:19:22 -05:00
