DNS server

Ditto.

eero software release notes suggests that it uses dnsmasq

https://support.eero.com/hc/en-us/articles/209636523-eero-Software-Release-Notes

dnsmasq supports a DNS service that will resolve local /etc/hosts entries. eero should provide a user interface to create such entries. Why don't they? It seems so simple.

This could be done explicitly with a host name/address UI and/or implicitly by, say, using the name on a static DHCP lease.

Every (cheap) ISP router I have ever had has provided a local DNS service that I have used to internally publish the names and addresses of my local machines. It's just mind-boggling why such an expensive eero solution can't do the same - especially when its underlying software (dnsmasq) can easily be configured to do so.

Please.

I would love to see the ability to add DNS entries or at least have eero automatically map nicknames.  It would also be nice to specify a custom domain.

For IPv6 support, it's necessary to have some way to resolve the hosts (Windows/Linux and Mac) on our local networks.

Please consider providing this functionality. Especially as I am an Eero Plus customer and by enabling Advanced Security I cannot change the DNS server IP provided by DHCP address leases. I understand this is due to the DNS entries being forwarded to zscaler, however we need a good way to serve local DNS entries. 

Certainly consider providing this.  I assumed it was already there and went to add an entry, and the feature is amiss.  This is a pretty high end device to not have such a low end type of capability.  Please consider this so our 300 dollar router is just as capable as our 30 dollar Netgear!

This would be amazing for when my ISP has outages, I will still be able to access home assistent via the dns name and have internal network ssl support.

Ubiquiti offers all we need by simply offering entry fields which can be appended as options, likely added as an additional config file:

dnsmasq --conf-file=eero.conf --conf-file=user-append.conf

This means we can add our own: 

dhcp-host=11:22:33:44:55:66,fred

.. entries and they'd be part of the Dnsmasq config.  I don't think Ubiquiti even sanity-checks the config items, they just let you keep adding text strings to the UI that they drop straight into a text file.

Of note, the example above is really an example of the power we're missing out on: I don't care what IP is given, just name this device by this macaddr "fred".  Thereafter, "ssh fred" works fine even if you change the subnet of the DHCP leases.  I have some 3 dozen lines like this one in my UBNT config that I turned off (all UBNT was doing at this point was leases -- I'd rather have my single-points-of-failure in the same eero box)

Holy Cow EeroA  What the hell?  *Every* router I've ever touched does this.  I just dropped  over $400 on an Eero system and it doesn't do this?  What gives?

Looking to implement wpad

Hey, Eero product management people... from one product person to another... please, oh please, bump this up on the backlog. 

Hey Eero;

FWIW I'm a software engineer and SRE with background in OpenWRT, Motorola embedded linux, Linux Foundation, LiMo, etc and I'm sure there are others in this group with better pedigree than that.  If you have a build framework and an NDA, I'll provide a suggestion in terms of a Pull Request and we can progress from platitudes and ignoring to bike-shedding nuances.

If you'd prefer to skip an NDA, just put some representation of your build logic, and share zero secrets with me, and we'll get 'er done that way.

If you don't know terms like "Pull Request", "bike-shedding:, and "build framework", please discuss with your Engineering Manager.  Motivated OpenSourcers are an untapped resource.

Can I vote more than once? I love my Eero and the Plus product. But I SO want to add DNS entries.

I agree this is a critical missing feature that every other router I've used has.  Since Eero is using dnsmasq as shown in the release notes referenced above it should be easy to implement.

We need this feature to allow named connections internally.  If I want to connect to my nas for instance from a mac I have to use its ip address instead of its easily remembered name.  I also have to configure a static address to maintain connections to the nas from clients that mount it.  With dnsmasq configured correctly we could use a name that is automatically updated to reflect the ip address handed out by dhcp.  Why is the reset of this product so awesome and this piece is stuck in 1998?

Now that the eero's internal DNS is advertised via DHCP and obviously more widely used... I can haz A records?

Yea.. Just bought this system and that really sucks not having any option to have Aliases or any DNS service within the box. 

This seems like a trivial change to me. Just add an OPTION to the EERO app to set a domain name (that ultimately gets propagated to DHCP clients). Then we can continue our own DNS servers

Please Please Please add this feature.

Surprised this still hasn’t been implemented yet for such an expensive router. I have a $20 TP-Link router I use for device testing and even it supports an internal DNS. Please add this feature!

Hey James

Imagine you run a server that's accessible to the outside world:

https://tiny-server.example.com
-> 992.10.45.99:443 (typical external IP)
-> Eero (sits at the top of the network, routing port 443 to the server)
-> 192.168.1.14:443 (internal server IP)

It would be amazing if we could configure custom DNS entries within Eero, so we can configure tiny-server.example.com to resolve to an internal IP instead of bouncing traffic out & in the network when accessed from within the network.

There are plenty of reasons to support this - ranging from business use-cases & software development to gaming. Currently solutions involve self-running a DNS server, or manually editing /etc/hosts files on machines.

Cheers,
James

This is one of the major road blocks to me subscribing to eero secure(+), you can’t use any of the features with manual dns. Would gladly disable my Pi-hole and use eero ad blocking if it could also resolve local host names for me. (Or allow me to at least forward ports without exposing them externally, either would really do)

I think this entire thread boils down to: 

Please make the internal DNS server reply to PTR record request for internal IP addresses (both IPv4 and IPv6)

Example:

nslookup 192.168.4.11 192.168.4.1

should return 

11.4.168.192.in-addr.arpa name = myDeviceName.

As many other people seem to have a similar story, I also just setup my eero for the first time and was astonished this is missing functionality. 

This thread is 4 years old, no updates in the last 3 months. Is there any further impression of where this sits on the backlog/priorities for an update? -- I'm left wondering if it's worth my time to implement a workaround or just return the product.

I would jump at the opportunity to even test this in preview with something from eero Labs.

Funny that eero's ddns feature was made to access LAN devices from WAN, but the "basic" use case (LAN-> LAN) is not there yet.. this is very interesting, since almost any $50 router can do this by default (dhcp ddns)

Not sure what is pushing them back on this, I don't know if this is just a feature "prioritization" in their backlog, or something that requires a complete architecture change and they can't afford it.

I really wanted to use eero as my router and have all the built in features enabled... but at this point, I will probably have to set them as "dumb" access points.

Wow, I can't believe I am finding this article. Is eero really only designed for consumers who use netbooks and IOT?

Kind of pathetic, but I guess that reflects the state of American innovation these days.