Node address does not resolve when dc contains capitals

[remmelt]

When resolving nodes with capitals, Consul reports that they are unknown.
CLI flags: -server -bootstrap -log-level=debug -dc Dc1
Consul versions tested: 0.4.1 and 0.5.0

I have registered a service 'test-service'.

$ dig @boot2docker -p 8600 test-service.service.consul. SRV

; <<>> DiG 9.8.3-P1 <<>> @boot2docker -p 8600 test-service.service.consul. SRV
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42604
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;test-service.service.consul.   IN  SRV

;; ANSWER SECTION:
test-service.service.consul. 0  IN  SRV 1 1 49171 node1.node.Dc1.consul.

;; ADDITIONAL SECTION:
node1.node.Dc1.consul.  0   IN  A   172.17.0.45

;; Query time: 1 msec
;; SERVER: 192.168.59.103#8600(192.168.59.103)
;; WHEN: Thu Mar  5 15:32:14 2015
;; MSG SIZE  rcvd: 144

The expected result is the correct IP address, as listed in the ADDTIONAL SECTION of the original response.

When doing an additional lookup for the node including the dc:

$ dig @boot2docker -p 8600 node1.node.Dc1.consul. ANY

; <<>> DiG 9.8.3-P1 <<>> @boot2docker -p 8600 node1.node.Dc1.consul. ANY
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25042
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;node1.node.Dc1.consul.     IN  ANY

;; Query time: 3 msec
;; SERVER: 192.168.59.103#8600(192.168.59.103)
;; WHEN: Thu Mar  5 15:33:46 2015
;; MSG SIZE  rcvd: 39

It does work without the dc:

$ dig @boot2docker -p 8600 node1.node.consul. ANY

; <<>> DiG 9.8.3-P1 <<>> @boot2docker -p 8600 node1.node.consul. ANY
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25971
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;node1.node.consul.     IN  ANY

;; ANSWER SECTION:
node1.node.consul.  0   IN  A   172.17.0.45

;; Query time: 1 msec
;; SERVER: 192.168.59.103#8600(192.168.59.103)
;; WHEN: Thu Mar  5 15:38:40 2015
;; MSG SIZE  rcvd: 68

These examples are using docker-consul but the same results apply when running consul natively.

According to the documentation, this should be supported.

[ryanuber]

Hey @remmelt, this definitely seems a bit odd. Thanks for letting us know, marking as a bug.