hi,
I’m trying to create some dns srv records using the web interface but I cannot understand where to put the protocol (es. tcp) info.
According to the data field, SRV records require priority weight port target of a server so I’m wondering how and where I have to put the proto.
thank a lot
ML
hi & thank you.
Unfortunately It doesn’t work even replacing record type with SRV
I tried a number of confs using myservice._tcp and _myservice._tcp but it doesn’t work.
I think the real problem is the web interface because when I try to remove/modify a record it simply doesn’t work, i mean the gui removes/modifies the record but if I use dig often the record isn’t deleted/modified.
hoipe this help
ML
I tried and it works on my end
Can you clarify if you are able to create a new record and properly resolve the dns query? Are you then facing issues in the update of such records?
funny,
but it doesn’t work for me.
I created a test domain and add a record (t1.test) and a service (myservice._tcp.test)
ubuntu@maas:~$ dig @localhost SRV myservice_.tcp.test
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> @localhost SRV myservice_.tcp.test
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30686
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 063803e152ea1b83010000006573375b77ea0b73bdcd9af8 (good)
;; QUESTION SECTION:
;myservice_.tcp.test. IN SRV
;; AUTHORITY SECTION:
test. 30 IN SOA test. nobody.example.com. 893 600 1800 604800 30
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Fri Dec 08 15:33:47 UTC 2023
;; MSG SIZE rcvd: 134
ubuntu@maas:~$ dig @localhost A t1.test
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> @localhost A t1.test
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52139
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 06c4597470e221e8010000006573376200d6884f76981e02 (good)
;; QUESTION SECTION:
;t1.test. IN A
;; ANSWER SECTION:
t1.test. 30 IN A 192.168.1.1
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Fri Dec 08 15:33:54 UTC 2023
;; MSG SIZE rcvd: 80
What Maas version are you using?
MAAS: 3.3.5 (upgraded from 3.3.3)
Same behaviour with 3.3.3
Do you have issues also with other record types?
Side question: any chance to test also on MAAS 3.2? We did some changes on 3.3 for DNS and I just want to be sure we don’t have any regression there
sorry, never used 3.2.
I think the problem is the dns upgrade from the web gui during SRV record management, for example now I’ve created a test domain with 3 A records (t1,t2,t3) and 3 SRV records
well, I can’t resolve it
ubuntu@maas:~$ dig @localhost SRV _myservice._tcp.test
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> @localhost SRV _myservice._tcp.test
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10147
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 547ae5a2c257bd99010000006574904fd254cfc1130a7ccc (good)
;; QUESTION SECTION:
;_myservice._tcp.test. IN SRV
;; AUTHORITY SECTION:
test. 30 IN SOA test. nobody.example.com. 957 600 1800 604800 30
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost) (UDP)
;; WHEN: Sat Dec 09 16:05:35 UTC 2023
;; MSG SIZE rcvd: 135
and
ubuntu@maas:~$ cat /var/lib/bind/maas/zone.test
; Zone file modified: 2023-12-09 16:00:59.338123.
$TTL 30
@ IN SOA test. nobody.example.com. (
0000000951 ; serial
600 ; Refresh
1800 ; Retry
604800 ; Expire
30 ; NXTTL
)
@ 30 IN NS maas.
t2 30 IN A 192.168.1.2
t3 30 IN A 192.168.1.3
t1 30 IN A 192.168.1.1
_mys._tcp 30 IN SRV 10 10 1234 t1
FYI _mys._tcp was a previous test I had made and then deleted but it keeps appearing 
It sounds to me that upgrading from the web gui sometimes goes wrong but the gui doesn’t recognize it and shows updates even the named conf is not properly modified/updated
ML
