dial tcp: lookup www.dyson.ch on 192.168.0.1:53: read udp 192.168.0.103:60923->192.168.0.1:53: i/o timeout

[NobinPegasus]

While running gobuster, dirbuster, feroxbuster, dirsearch from my kali VM I am facing this error.

error on running gobuster: unable to connect to https://www.dyson.ch/: Get "https://www.dyson.ch/": dial tcp: lookup www.dyson.ch on 192.168.0.1:53: read udp 192.168.0.103:60923->192.168.0.1:53: i/o timeout

My network configuration is Host only adapter and my host OS is Windows.

I tried changing my network configuration. I tried with host only adapter, bridge adapter and NAT.

 

[CaffeineAddict]

The problem you're having is likely DNS misconfiguration, so I'd start by troubleshooting this first.

use dig program to test DNS and watch firewall logs to see if your NAT works as it should.

 

[NobinPegasus]

All websites work well from browser inside Kali VM.
But the buster tools aren't working.
The output of dif is given:

[LIST=1]
[*]; <<>> DiG 9.20.0-Debian <<>> www.dyson.ch
[*];; global options: +cmd
[*];; Got answer:
[*];; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16100
[*];; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
[*]
[*];; OPT PSEUDOSECTION:
[*]; EDNS: version: 0, flags:; udp: 512
[*];; QUESTION SECTION:
[*];www.dyson.ch.                  IN      A
[*]
[*];; ANSWER SECTION:
[*]www.dyson.ch.           300     IN      CNAME   www2.dyson.com.edgekey.net.
[*]www2.dyson.com.edgekey.net. 300 IN      CNAME   e29302.a.akamaiedge.net.
[*]e29302.a.akamaiedge.net. 20     IN      A       23.57.76.55
[*]e29302.a.akamaiedge.net. 20     IN      A       23.57.76.63
[*]
[*];; Query time: 431 msec
[*];; SERVER: 192.168.0.1#53(192.168.0.1) (UDP)
[*];; WHEN: Wed Aug 21 17:48:48 EDT 2024
[*];; MSG SIZE  rcvd: 147
[/LIST]

@CaffeineAddict

 

[CaffeineAddict]

All websites work well from browser inside Kali VM.
But the buster tools aren't working.
The output of dif is given:

[LIST=1]
[*]; <<>> DiG 9.20.0-Debian <<>> www.dyson.ch
[*];; global options: +cmd
[*];; Got answer:
[*];; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16100
[*];; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
[*]
[*];; OPT PSEUDOSECTION:
[*]; EDNS: version: 0, flags:; udp: 512
[*];; QUESTION SECTION:
[*];www.dyson.ch.                  IN      A
[*]
[*];; ANSWER SECTION:
[*]www.dyson.ch.           300     IN      CNAME   www2.dyson.com.edgekey.net.
[*]www2.dyson.com.edgekey.net. 300 IN      CNAME   e29302.a.akamaiedge.net.
[*]e29302.a.akamaiedge.net. 20     IN      A       23.57.76.55
[*]e29302.a.akamaiedge.net. 20     IN      A       23.57.76.63
[*]
[*];; Query time: 431 msec
[*];; SERVER: 192.168.0.1#53(192.168.0.1) (UDP)
[*];; WHEN: Wed Aug 21 17:48:48 EDT 2024
[*];; MSG SIZE  rcvd: 147
[/LIST]

Therefore problem is not with DNS but with the specific tools you're using.
See if they have some configuration files associated with them, and if so verify they're correct.

It might be configuration error or a bug.

 

[NobinPegasus]

Therefore problem is not with DNS but with the specific tools you're using.
See if they have some configuration files associated with them, and if so verify they're correct.

It might be configuration error or a bug.

They don't have any config file.
And it works on any host unix distro. But in virtualbox I'm facing the problem

 

[CaffeineAddict]

And it works on any host unix distro. But in virtualbox I'm facing the problem

Can't help with VirtualBox, but I'd personally use Hyper-V on Windows unless your edition is "home"

 

[GatorsFan]

it looks like www.dyson.ch does not exist try https://www.dyson.com/en or https://www.dyson.ch/de