FPP Install on Raspberry Pi Zero W

[Poporacer]

I would not put my Home Router as a first (or second) DNS choice.

There are many routers out there that do not process a direct DNS request and will use their own internal DNS request method, so it is recommended to use your router's IP address for one of your DNS server addresses and your router will then use its own DNS request method to get the correct IP address.

In regard to first or second requests, those are not sequential requests, they are simultaneous requests and whoever answers first is the address that gets used. 

[k6ccc]

In regard to first or second requests, those are not sequential requests, they are simultaneous requests and whoever answers first is the address that gets used.

I don't know about Linux (and variants), but that is not correct at least with Windows.  There are several steps before the computer will even check a DNS server (local cache, hosts files, and a couple others), but that's not really the discussion.  Once those are exhausted, a DNS server will be queried.  If you only have one DNS server listed, that is the DNS server that will be queried (DUH).  If you have multiple DNS servers listed, which one is used depends on which version of Windows.  Prior to Windows 10, the binding order (in other words which one is listed first) is what matters.  In windows 10 and later, the metric (or routing cost) is used.  If listed, your local router will be the lowest routing cost, so that will be used (for Windows 10 and newer).  The only time the second DNS server will be queried BY YOUR COMPUTER is if the first DNS server fails to respond within the timeout period.  More on that later.

Whatever DNS server your computer queries may or may not be able to resolve the IP of what you are looking for.  However generally that DNS server will have a higher level DNS server that it can query..  This can progress several steps.  For example, let's say that your local computer was given the address of your local router as it's DNS provider (very common when you get a DHCP address from your local router).  Your local router in turn got a DHCP address from your ISP and that included a DNS server to use (likely a server that your ISP provides).  Eventually if not found the query will be going to the root server for the Top Level Domain (for example .com).  If there is no resolution, that fact will go back down the chain to your computer with an unable to resolve message.  As long as your computer gets a response (including an unable to resolve) it WILL NOT try another DNS server.

If your computer has multiple DNS servers listed and it does not get any reply from the first DNS server within the timeout, it will try the second DNS server listed (either by binding order or route cost depending on Windows version).  Once all listed DNS servers have failed to respond, then there are several steps involving progressively longer timeouts and different interfaces.  Eventually it will get to a shotgun blast to all DNS servers listed on all interfaces, but there has to be a lot of failures to respond to get to that point.  If ANY DNS server responds with either the resolved IP address or an unable to resolve message, the process stops.

[Poporacer]

You obviously have more knowledge than I do in regard to this and maybe my old mind is remembering things incorrectly, but I DO KNOW that I have helped dozens of people, if not more, that in FPP they could not update due to not resolving github.com address using 8.8.8.8 (or other internet based address) but as soon as they added their router's IP address as a DNS server it worked. Fluke? Maybe but that resolved many update issues I have seen.

[pixelpuppy]

I would not put my Home Router as a first (or second) DNS choice. Maybe your router is smarter than mine, but mine does not know any significant DNS information. I put 8.8.8.8 as my first choice.

It probably 'knows' more than you think.  Unless its ancient, virtually all modern home routers do DNS caching.  Its not a full blown DNS server, but acts like a DNS proxy (with local caching) to the (usually) ISP's DNS server.  Putting the Home Router first in the list gives you faster lookups for frequently accessed DNS names.  In all fairness, 8.8.8.8 is pretty damn fast and I doubt most humans would notice and difference either way.  But conceptually, there is a rhyme and reason to putting the home router as the first DNS server.

[k6ccc]

Correct.  I did not mention caching - which damn near any DNS server (including your home router) does.  There are several parameters (which on consumer equipment, you have no control of) that determines how long cached data is retained.