UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
While this bug is filed under Windows it's also affecting Chrome OS on Chromebooks.

The problem is that Chrome keeps losing "(local)" variants of printers. It started off as a bug here https://github.com/google/cups-connector/issues/200 but seems to be a Chrome bug instead.

What I'm seeing is that Chrome sends privet requests before mDNS responses are received. So if a local printer is in the mDNS cache it will work fine but if the cache has expired then Chrome will never query the printer for privet info.

0. Make sure your OS isn't running some kind of local mDNS server that can reply quicker than any network traffic. For example my Android phone doesn't display this bug and it seems to be running an mDNS server for googlecast.

1. Use some kind of network monitoring tool.

2. Open a print dialog in Chrome and then go to change printers and select your locally shared printer. This should fill your cache and get you in the same starting position.

3. But don't print anything. Just close that print dialog and refresh the page.

4. Open another print dialog. You should see the following traffic:
4.1. One or more mDNS requests
4.2. A HTTP privet request
4.3. A HTTP privet response
4.4. One or more mDNS responses

5. Again don't print anything. Close the dialog, refresh the page, and wait ten or so minutes for Chrome to clear it's cache (clearing the main net-internals DNS cache doesn't seem to affect the mDNS cache).

6. Open a new print dialog. You know the cache is empty when you see the loading spinner next to your printer and no printer options below it. You should see the following traffic:
6.1. One or more mDNS requests
6.2. No HTTP requests (the mDNS cache is presumably empty after step 5).
6.3. One or more mDNS responses

7. Click change printer. You should see the following traffic:
7.1. One or more mDNS requests
7.2. A HTTP privet request (the mDNS cache is presumably primed after step 6.3)
7.3. A HTTP privet response
7.4. One or more mDNS responses

What is the expected behavior?
GCP 2.0 local printers should always appear.

What went wrong?
GCP 2.0 local printers keep disappearing, sometimes for a few seconds, sometimes for 10 minutes.

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

If a local printer disappears after clicking the "print" button but before the UI closes then Chrome will revert to the OS default printer and send the job to the wrong location.