coredns_omada.init calls dnsserver.init, which calls doh.init

coredns_omada.init calls file.init, which calls dnsutil.init

coredns_omada.Omada.ServeDNS calls file.Zone.Lookup, which eventually calls dnsutil.Join

coredns_omada.init calls dnsserver.init

coredns_omada.Omada.ServeDNS calls dnsserver.gRPCresponse.WriteMsg

coredns_omada.Omada.ServeDNS calls request.ScrubWriter.WriteMsg, which eventually calls dnsserver.gRPCresponse.RemoteAddr

coredns_omada.Omada.ServeDNS calls file.Zone.Lookup, which eventually calls dnsserver.Server.ServeDNS

coredns_omada.Omada.ServeDNS calls dnsserver.DoHWriter.WriteMsg

coredns_omada.Omada.ServeDNS calls request.ScrubWriter.WriteMsg, which eventually calls dnsserver.DoHWriter.RemoteAddr

coredns_omada.init calls plugin.init, which calls cidr.init

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/checkout@v4.1.1, actions/setup-go@v5, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/