Skip to content
Discussion options

You must be logged in to vote

Hi @daiwei-china - thanks for the additional detail. The DNS setting is the cause. I reproduced your setup in a lab to confirm: host A on Debian 13 and host B on Windows 10, both running official Nebula v1.11.0 binaries with your configs, and B's Nebula adapter DNS set to 10.10.19.3.

Results (uncached DNS lookup / HTTP page fetch):

┌──────────────────────┬──────────────────┬─────────────┬────────────┬────────────┐
│       Scenario       │ lighthouse.hosts │ Adapter DNS │ DNS lookup │ HTTP fetch │
├──────────────────────┼──────────────────┼─────────────┼────────────┼────────────┤
│ Baseline (no Nebula) │ -                │ -           │ 29-50 ms   │ 116 ms     │
├──────────────────────┼───…

Replies: 1 comment 8 replies

Comment options

You must be logged in to vote
8 replies
@daiwei-china
Comment options

@johnmaguire
Comment options

@daiwei-china
Comment options

@johnmaguire
Comment options

Answer selected by johnmaguire
@daiwei-china
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1830 on July 31, 2026 20:20.