Hi Robert,
It supports DNS A records, but not a DNS SRV record. At least not in my direct testing. The only workaround I found was resolving the SRV to the child A records like this redacted example
```
computer ~ % dig srv my.srv.domain.tld
; <<>> DiG 9.10.6 <<>> srv my.srv.domain.tld
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27807
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;my.srv.domain.tld. IN SRV
;; ANSWER SECTION:
my.srv.domain.tld. 300 IN SRV 1 10 5060 sbc1.domain.tld.
my.srv.domain.tld. 300 IN SRV 1 10 5060 sbc2.domain.tld.
my.srv.domain.tld. 300 IN SRV 1 10 5060 sbc3.domain.tld.
```
I then add the FQDN's for each of the answers (sbc1, sbc2, sbc3) to the Outbound section of the BYOC trunk and they'd be added to the ACL as well.
However, this workaround is subject to failure/issues if/when the SRV is updated, thus defeating the purpose of using SRV. Genesys uses SRV for inbound so they can remove/update the region-specific load balancers as needed, but it would appear this is not supported for outbound traffic.
------------------------------
Paul McGurn
Manager, Telecom Services
GoTo
------------------------------
Original Message:
Sent: 06-08-2023 18:30
From: Robert Wakefield-Carl
Subject: DNS SRV support for outbound BYOC trunk?
The SIP Proxy field should support an outbound DNS. See this:

I would guess the ACL is not populated with the correct IP range. That does not support DNS.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 06-07-2023 13:35
From: Paul McGurn
Subject: DNS SRV support for outbound BYOC trunk?
I know DNS SRV is supported for inbound, but it doesn't seem to work for outbound. When I configure a SRV address in the outbound proxy addresses section, and attempt to dial through to it, the calls fail in less than 100ms, which leads me to believe GCCX isn't resolving the addresses. There's no capture on the interaction detail, either, so it's failing before it even gets to the point where a PCAP would be generated. The documentation for External Trunk > Outbound doesn't indicate whether or not this is supported, either.
#Telephony
------------------------------
Paul McGurn
Manager, Telecom Services
GoTo
------------------------------