Nik Martin created CLOUDSTACK-282:
-------------------------------------
Summary: Virtual Routers do not properly resolve DNS SRV Records
Key: CLOUDSTACK-282
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-282
Project: CloudStack
Issue Type: Bug
Components: Network Controller
Affects Versions: pre-4.0.0
Environment: Cloudstack 3.02 Management Server on Centos 6.2,
Xenserver 6.02 Hosts
Reporter: Nik Martin
Priority: Minor
When using SNAT Networking, I have a VM with a Static NAT IP Assinged in
Cloudstack. The Centos 6.2 VM has dhcp defined as the network protocol, and
gets a private network IP, and a Static NAT Public IP. /etc/resolv.conf on the
guest VM gets written out by dhclient, and has one nameserver defined:
10.1.1.1, which is the virtual router for the guest network. If doing a DIG
lookup of a SRV record in the form:
# dig _sip._tcp.voipstack.net SRV
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.4 <<>> _sip._tcp.voipstack.net
SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 576
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;_sip._tcp.voipstack.net. IN SRV
;; Query time: 1 msec
;; SERVER: 10.1.1.1#53(10.1.1.1)
;; WHEN: Sun Oct 7 13:40:43 2012
;; MSG SIZE rcvd: 41
Nothing is returned.
If I manually edit /etc/resolv.conf, and add: nameserver 8.8.8.8, and do the
same query, I get:
# dig _sip._tcp.voipstack.net SRV
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.4 <<>> _sip._tcp.voipstack.net
SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42375
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;_sip._tcp.voipstack.net. IN SRV
;; ANSWER SECTION:
_sip._tcp.voipstack.net. 1606 IN SRV 1 9 5060 as2.voipstack.net.
_sip._tcp.voipstack.net. 1606 IN SRV 0 9 5060 as1.voipstack.net.
;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Oct 7 13:33:39 2012
;; MSG SIZE rcvd: 115
The virtual router should resolve all valid DNS record types
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
