[roll] Roll fuchsia [netcfg] Transmit Delegated DNS through NetworkRegistry

Netcfg now learns about delegated DNS servers through the
DelegatedNetworks registry rather than through socket-proxy's
DnsServerWatcher. This sets up the future scenario where netcfg
will be the source-of-truth for network information and Starnix
will communicate directly with netcfg for network information.

DNS servers are returned from the network registry update functions
so that these servers can be communicated to dns-resolver's
LookupAdmin.

Existing tests within policy-management-integration-test and
netstack-dns-integration-test confirm that these changes maintain
current behavior.

Original-Original-Bug: 475916525
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1594351
Original-Original-Revision: 19e77c950279870eec154639adcd146982b57913
GitOrigin-RevId: d10764ad56c4a1aa500011f6fa231a8818f6825f
Change-Id: I5d9ab4c775996911ffe8107b5f9a4bc725323116
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1611651
Cr-Commit-Position: refs/heads/main@{#192761}
1 file changed
tree: eacf63d7e8d379661efb565344dc0c3ccb2efcdf
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.