dnsvi creates broken srv records? #11

New issue

Closed

opened 2026-10-14 15:36:04 +02:00 by mf · 1 comment

mf commented

2026-10-14 15:36:04 +02:00

Owner

dnsvi -l somezone on our master currently results in the following output after quitting the editor (not actually editing anything) and typing 'v' (for verbosity i guess):

added: 5, removed: 5
action [yqQvVeu?] ?
The following changes need your confirmation.
 - _caldavs._tcp.somezone. 3600 SRV 10 1 443 egroupware.somezone. 
 - _smtp._tcp.somezone. 3600 SRV 10 1 587 mail.somezone. 
 - _carddavs._tcp.somezone. 3600 SRV 10 1 443 egroupware.somezone. 
 - _imap._tcp.somezone. 3600 SRV 10 1 143 mail.somezone. 
 - _imaps._tcp.somezone. 3600 SRV 10 1 993 mail.somezone. 
 + _caldavs._tcp.somezone. 3600 SRV 10 1 443 egroupware 
 + _smtp._tcp.somezone. 3600 SRV 10 1 587 mail 
 + _imap._tcp.somezone. 3600 SRV 10 1 143 mail 
 + _imaps._tcp.somezone. 3600 SRV 10 1 993 mail 
 + _carddavs._tcp.somezone. 3600 SRV 10 1 443 egroupware 
action [yqQvVeu?] ?

I guess the issue is twofold.

The editor actually shows the records that are supposed to be added as written in the output. There is probably an issue in setting up the file to edit.
Accepting the proposed edits results in broken srv records (something adds a trailing dot to the target)

$ dig srv _imap._tcp.somezone @pu.schlittermann.de

; <<>> DiG 9.18.49-1~deb12u2-Debian <<>> srv _imap._tcp.somezone @pu.schlittermann.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30208
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 71c26033b3094d2f010000006acf8200cc8eefc2e0b57872 (good)
; EDE: 18 (Prohibited)
;; QUESTION SECTION:
;_imap._tcp.somezone.    IN      SRV

;; ANSWER SECTION:
_imap._tcp.somezone. 3600 IN     SRV     10 1 143 mail.

;; Query time: 28 msec
;; SERVER: 91.204.45.205#53(pu.schlittermann.de) (UDP)
;; WHEN: Wed Oct 14 15:22:08 CEST 2026
;; MSG SIZE  rcvd: 113

`dnsvi -l somezone` on our master currently results in the following output after quitting the editor (not actually editing anything) and typing 'v' (for verbosity i guess): ``` added: 5, removed: 5 action [yqQvVeu?] ? The following changes need your confirmation. - _caldavs._tcp.somezone. 3600 SRV 10 1 443 egroupware.somezone. - _smtp._tcp.somezone. 3600 SRV 10 1 587 mail.somezone. - _carddavs._tcp.somezone. 3600 SRV 10 1 443 egroupware.somezone. - _imap._tcp.somezone. 3600 SRV 10 1 143 mail.somezone. - _imaps._tcp.somezone. 3600 SRV 10 1 993 mail.somezone. + _caldavs._tcp.somezone. 3600 SRV 10 1 443 egroupware + _smtp._tcp.somezone. 3600 SRV 10 1 587 mail + _imap._tcp.somezone. 3600 SRV 10 1 143 mail + _imaps._tcp.somezone. 3600 SRV 10 1 993 mail + _carddavs._tcp.somezone. 3600 SRV 10 1 443 egroupware action [yqQvVeu?] ? ``` I guess the issue is twofold. 1) The editor actually shows the records that are supposed to be added as written in the output. There is probably an issue in setting up the file to edit. 2) Accepting the proposed edits results in broken srv records (something adds a trailing dot to the target) ``` $ dig srv _imap._tcp.somezone @pu.schlittermann.de ; <<>> DiG 9.18.49-1~deb12u2-Debian <<>> srv _imap._tcp.somezone @pu.schlittermann.de ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30208 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 71c26033b3094d2f010000006acf8200cc8eefc2e0b57872 (good) ; EDE: 18 (Prohibited) ;; QUESTION SECTION: ;_imap._tcp.somezone. IN SRV ;; ANSWER SECTION: _imap._tcp.somezone. 3600 IN SRV 10 1 143 mail. ;; Query time: 28 msec ;; SERVER: 91.204.45.205#53(pu.schlittermann.de) (UDP) ;; WHEN: Wed Oct 14 15:22:08 CEST 2026 ;; MSG SIZE rcvd: 113 ```

mf added the

bug

label

2026-10-14 15:46:40 +02:00

mf commented

2026-10-14 15:47:16 +02:00

Author

Owner

The first issue can be worked around partially by adding .somezone. to the targets of the srv records, but dnsvi fails to detect these and any additional actual changes to the zone instead, preventing me from actually editing the zone at all.

Update: The additional actual changes to the zone mentioned above were probably not detected because they were probably already part of the zone. I cannot reproduce that part of the issue currently.

The first issue can be worked around partially by adding `.somezone.` to the targets of the srv records, but `dnsvi` fails to detect these and any additional actual changes to the zone instead, preventing me from actually editing the zone at all. Update: The additional actual changes to the zone mentioned above were probably not detected because they were probably already part of the zone. I cannot reproduce that part of the issue currently.

mf referenced this issue from a commit

2026-10-14 16:12:20 +02:00

FIX: Qualify relative SRV targets with the origin (closes #11)

mf closed this issue

2026-10-14 16:12:20 +02:00

mf referenced this issue

2026-10-20 14:40:09 +02:00

IDN conversion dies on null target "." (MX, SRV) ai:claude-opus-5-5 #12