Skip to main content
Became Hot Network Question
edit info
Source Link
nullromo
  • 391
  • 2
  • 11

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

Additional Info

I can access my device from Google Chrome just fine using the hostname. I also tried Resolve-DnsName gp800-49d1a in PowerShell, and it works correctly. It seems both Chrome, PowerShell, and WSL know how to find the mDNS entry, but nslookup from Windows Command Prompt does not.

Question

Since nslookup doesn't find my device from Windows Command Prompt, what else can I use to get the IP address of my device from Windows?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

Additional Info

I can access my device from Google Chrome just fine using the hostname. I also tried Resolve-DnsName gp800-49d1a in PowerShell, and it works correctly. It seems Chrome, PowerShell, and WSL know how to find the mDNS entry, but nslookup from Windows Command Prompt does not.

Question

Since nslookup doesn't find my device from Windows Command Prompt, what else can I use to get the IP address of my device from Windows?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

Additional Info

I can access my device from Google Chrome just fine using the hostname. It seems both Chrome and WSL know how to find the mDNS entry, but nslookup from Windows Command Prompt does not.

Question

Since nslookup doesn't find my device from Windows Command Prompt, what else can I use to get the IP address of my device from Windows?

add additional information
Source Link
nullromo
  • 391
  • 2
  • 11

Why doesn't How can I perform an mDNS lookup on Windows nslookup detect my device?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

Additional Info

I can access my device from Google Chrome just fine using the hostname. I also tried Resolve-DnsName gp800-49d1a in PowerShell, and it works correctly. It seems Chrome, PowerShell, and WSL know how to find the mDNS entry, but nslookup from Windows Command Prompt does not.

Question

Since nslookup doesn't find my device from Windows Command Prompt, what else can I use to get the IP address of my device from Windows?

Why doesn't Windows nslookup detect my device?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

How can I perform an mDNS lookup on Windows?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.

Additional Info

I can access my device from Google Chrome just fine using the hostname. I also tried Resolve-DnsName gp800-49d1a in PowerShell, and it works correctly. It seems Chrome, PowerShell, and WSL know how to find the mDNS entry, but nslookup from Windows Command Prompt does not.

Question

Since nslookup doesn't find my device from Windows Command Prompt, what else can I use to get the IP address of my device from Windows?

Source Link
nullromo
  • 391
  • 2
  • 11

Why doesn't Windows nslookup detect my device?

Background

I have a device plugged into my Windows PC via Ethernet. The device is running an mDNS service and has its own hostname (gp800-49d1a).

From WSL, I can ping gp800-49d1a with success, and I can nslookup gp800-49d1a with the following result:

Server:         172.30.176.1
Address:        172.30.176.1#53

Non-authoritative answer:
Name:   gp800-49d1a.local
Address: 169.254.93.130
Name:   gp800-49d1a.local
Address: fe80::e700:63f:1807:adf2

I can get the IP address 169.254.93.130. Connecting on this address works. Everything is correct up to this point.

Problem

When I run nslookup gp800-49d1a from Windows Command Prompt, I get the following result:

Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find gp800-49d1a: Non-existent domain

When I run ping gp800-49d1a from Windows Command Prompt, it works fine.

So for some reason nslookup from WSL is OK, but nslookup from Windows is not.