Domain Sniffing Cannot Handle Domains That Cannot Be Resolved

[changyp6]

Please read the instruction and answer the following questions before submitting your issue. Thank you.
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

1. What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
   Latest Git version

2. What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.

V2ray in Router, proxy all

3. What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)

Yeelight lamp tried to connect to "Mijia Cloud", "Mijia Cloud" is sniffed by V2ray, however, "Mijia Cloud" cannot be resolved by ordinary DNS server.
That's because the IP address of "Mijia Cloud" is hard coded into the Yeelight lamp, it is not using the DNS server to resolve the IP address. In this case, the domain sniffed by v2ray is a dummy domain, which cannot be resolved.

When it cannot be resolved, the lamp is disconnected from the cloud.

4. What's your expectation?
   When the Domain Name cannot be resolved, just use the original IP address, to make it work.

[kslr]

But the scope of use is very small, I suggest you try https://v2ray.com/chapter_02/03_routing.html

[changyp6]

Thank you for your suggestion. I've tweaked some of the code to ignore invalid domain name. For example, when there's space character in domain name, this domain must be invalid, just ignore it, and use it as is.

…

On Tue, Oct 8, 2019 at 11:39 PM Kslr ***@***.***> wrote: But the scope of adaptation is very small, I suggest you try https://v2ray.com/chapter_02/03_routing.html — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1913?email_source=notifications&email_token=ABPLTYNDZPULWXJBT3YIMCDQNSSR7A5CNFSM4I34CYWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAUTYUQ#issuecomment-539573330>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPLTYPNC2GU5MD6UCCWUJ3QNSSR7ANCNFSM4I34CYWA> .

[coppercash]

I tried freedom + AsIs.
But v2ray still went with tcp:Mijia Cloud:443.
Apparently, no DNS knows what the hell "Mijia Cloud" is (so ugly).

Now I am using:

{
  "tag": "mijia_cloud",
  "protocol": "freedom",
  "redirect": "58.83.177.143:0",
  …
}

I got the IP address with tcpdump.
Anyone knows how to let v2ray go with the IP directly?
So that I won't need to hard code it in my config.

[wych42]

But the scope of use is very small, I suggest you try https://v2ray.com/chapter_02/03_routing.html

But routing does not work, v2ray would dispatch connect to 'Mijia Cloud:443' not its original address 'ip:443'.

[rhhu]

I encountered the same problem. Could anyone tell me how to solve this?

[rockxsj]

I tried freedom + AsIs. But v2ray still went with tcp:Mijia Cloud:443. Apparently, no DNS knows what the hell "Mijia Cloud" is (so ugly).

Now I am using:

{
  "tag": "mijia_cloud",
  "protocol": "freedom",
  "redirect": "58.83.177.143:0",
  …
}

I got the IP address with tcpdump. Anyone knows how to let v2ray go with the IP directly? So that I won't need to hard code it in my config.

Hi, I get the same problem, could you share me your full config please? 💯