nebula
nebula copied to clipboard
Published
20 hours ago •
slackhq
slackhq
DNS server should resolve lighthouse hosts
Description:
When utilizing the dns listener serve_dns on any number of lighthouses, it is expected that the dns listener can also resolve the lighthouse along with other hosts.
Expected Behavior: Where
- lighthouse IP is 10.0.0.1
- lighthouse name is lighthouse.mesh.example.com
>> dig @10.0.0.1 lighthouse.mesh.example.com
; <<>> DiG 9.10.6 <<>> @10.0.0.1 lighthouse.mesh.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4452
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;lighthouse.mesh.example.com. IN A
;; ANSWER SECTION:
lighthouse.mesh.example.com. 3600 IN A 10.0.0.1
;; Query time: 55 msec
;; SERVER: 10.0.0.1#53(10.0.01)
;; WHEN: Wed Oct 27 10:46:58 CDT 2021
;; MSG SIZE rcvd: 94
Current Behavior:
>>dig @10.0.0.1 lighthouse.mesh.example.com
; <<>> DiG 9.10.6 <<>> @10.0.0.1 lighthouse.mesh.example.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10146
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;lighthouse.mesh.example.com. IN A
;; Query time: 55 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Wed Oct 27 10:51:24 CDT 2021
;; MSG SIZE rcvd: 46
Would love to see this as well, it causes me to need to handle some weird edge cases in the infrastructure I've built on top of nebula.
