Baniel Uri-CUB001 <[EMAIL PROTECTED]> writes:
>Say a SIP client is sending an SRV type of query to a DNS server in
>order to locate the appropriate SIP server. What would typically come
>back from the DNS server? Is it only the host name of the SIP server,
>or the IP address as well?
That depends on your nameserver. Bind version 9, for instance,
is intelligent enough to return all relevant A, AAAA and A6
records, too (if they fit in the response message).
Pekka
$ dig @127.0.0.1 example.com naptr
; <<>> DiG 9.2.1 <<>> @127.0.0.1 example.com naptr
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53887
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 1, ADDITIONAL: 11
;; QUESTION SECTION:
;example.com. IN NAPTR
;; ANSWER SECTION:
example.com. 60 IN NAPTR 80 50 "s" "SIP+D2T" ""
_sip._tcp.example.com.
example.com. 60 IN NAPTR 90 50 "s" "SIPS+D2T" ""
_sips._tcp.example.com.
example.com. 60 IN NAPTR 40 50 "s" "SIP+D2U" ""
_sip._udp.example.com.
;; AUTHORITY SECTION:
example.com. 60 IN NS ns.example.com.
;; ADDITIONAL SECTION:
sip02.example.com. 60 IN A 194.2.188.135
sip02.example.com. 60 IN A6 0
3ffe:1200:3012:c000:206:5bff:fe55:462f
sip00.example.com. 60 IN A 194.2.188.133
sip00.example.com. 60 IN A6 0
3ffe:1200:3012:c000:2c0:95ff:fee2:4b78
sip01.example.com. 60 IN A 194.2.188.134
sip01.example.com. 60 IN A6 0
3ffe:1200:3012:c000:a08:20ff:fe7d:e7ac
ns.example.com. 60 IN A 194.2.188.133
ns.example.com. 60 IN A6 0
3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
_sip._udp.example.com. 60 IN SRV 1 100 5060 sip00.example.com.
_sip._udp.example.com. 60 IN SRV 1 100 5060 sip01.example.com.
_sip._udp.example.com. 60 IN SRV 1 50 5060 sip02.example.com.
;; Query time: 55 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jul 14 07:49:27 2002
;; MSG SIZE rcvd: 507
$ dig @127.0.0.1 _sip._udp.example.com srv
; <<>> DiG 9.2.1 <<>> @127.0.0.1 _sip._udp.example.com srv
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40117
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 1, ADDITIONAL: 8
;; QUESTION SECTION:
;_sip._udp.example.com. IN SRV
;; ANSWER SECTION:
_sip._udp.example.com. 60 IN SRV 1 100 5060 sip01.example.com.
_sip._udp.example.com. 60 IN SRV 1 50 5060 sip02.example.com.
_sip._udp.example.com. 60 IN SRV 1 100 5060 sip00.example.com.
;; AUTHORITY SECTION:
example.com. 60 IN NS ns.example.com.
;; ADDITIONAL SECTION:
sip02.example.com. 60 IN A 194.2.188.135
sip02.example.com. 60 IN A6 0
3ffe:1200:3012:c000:206:5bff:fe55:462f
sip00.example.com. 60 IN A 194.2.188.133
sip00.example.com. 60 IN A6 0
3ffe:1200:3012:c000:2c0:95ff:fee2:4b78
sip01.example.com. 60 IN A 194.2.188.134
sip01.example.com. 60 IN A6 0
3ffe:1200:3012:c000:a08:20ff:fe7d:e7ac
ns.example.com. 60 IN A 194.2.188.133
ns.example.com. 60 IN A6 0
3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
;; Query time: 52 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jul 14 07:49:59 2002
;; MSG SIZE rcvd: 347
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
