NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Local Domain ping - name.local
I currently run my orbi in AP mode, and have a generic linksys acting as my "router" and it also broadcasting an additional wireless network. My problem is, when I am attached to the ORBI network, I...
.local domain name resolution typically uses mDNS. mDNS uses link-local IP multicast. Any kind of multicast is generally problematic for Wi-Fi. It's really hard to reliably reach ALL devices with a single transmission. To keep this manageable, many Wi-Fi stations will limit the speed of multicast transmissions. It's possible that the Orbi a very low limit. Unfortunately, Netgear doesn't usually expose any multicast speed settings.
I don't have an Orbi but maybe someone else can confirm the same behavior on their Orbi.
I don't have an Orbi but maybe someone else can confirm the same behavior on their Orbi.
Thanks for the reply. I am not sure if this is the problem. I have my own DNS setup on my network and all domain queries are coming through except for the .local resolution. Like stated before, when I get onto the Linksys wireless on the same subnet I have no issues reaching the .local domain.
I am not sure if anyone cares at this point. But what I have found out is, DNS behavior is different depending on the mode you are in, Router or AP mode.
1 - Router mode (no wire in "internet" port)
- I am able to ping my local domain
- all functionality words
2 - AP mode
- DNS is filtered and does not allow ping of local domain
Why do you think this is?
Thanks!
I am not sure if anyone cares at this point. But what I have found out is, DNS behavior is different depending on the mode you are in, Router or AP mode.
1 - Router mode (no wire in "internet" port)
- I am able to ping my local domain
- all functionality words
2 - AP mode
- DNS is filtered and does not allow ping of local domain
Why do you think this is?
Thanks!