Closed njam closed 7 years ago
@njam before I commit this, can you give me the backstory on what has led to this PR? The fix seems benign, so I am thinking we should just commit it.
I just stumbled upon this, while working on something else.
I'm not sure why 10.0.2.2 works, but both addresses seem to work equally well:
# dig @10.0.2.2 -p 10053 www.cm.dev.cargomedia.ch
[…|
;; ANSWER SECTION:
www.cm.dev.cargomedia.ch. 0 IN A 10.10.10.13
;; Query time: 7 msec
;; SERVER: 10.0.2.2#10053(10.0.2.2)
;; WHEN: Thu Aug 18 15:17:34 2016
;; MSG SIZE rcvd: 58
# dig @10.0.2.3 -p 10053 www.cm.dev.cargomedia.ch
[…]
;; ANSWER SECTION:
www.cm.dev.cargomedia.ch. 0 IN A 10.10.10.13
;; Query time: 7 msec
;; SERVER: 10.0.2.3#10053(10.0.2.3)
;; WHEN: Thu Aug 18 15:17:39 2016
;; MSG SIZE rcvd: 58
Cool. I am planning to merge #249 on Monday/Tuesday and prep a release. If this isn't already merged, I will merge it at that time too.
Merged as 1df24371fc98f69f045d054a692be38d2330b32e
Reverting as @hferentschik would like to discuss this further.
agree
we can leave 10.0.2.2 as nobody complained so far, and it worked just fine
Both work for me, but I think 10.0.2.3 is correct.