anchor.diff:  [id="nw-dns-forward_{context}"]
   = Using DNS forwarding
   
  -You can use DNS forwarding to override the forwarding configuration identified in `/etc/resolv.conf` on a per-zone basis by specifying which name server should be used for a given zone. If the forwarded zone is the Ingress domain managed by {product-title}, then the upstream name server must be authorized for the domain.
  +You can use DNS forwarding to override the default forwarding configuration in the `/etc/resolv.conf` file in the following ways:
  +
  +* Specify name servers for every zone. If the forwarded zone is the Ingress domain managed by {product-title}, then the upstream name server must be authorized for the domain.
  +* Provide a list of upstream DNS servers.
  +* Change the default forwarding policy.
  +
  +[NOTE]
  +=====
  +A DNS forwarding configuration for the default domain can have both the default servers specified in the `/etc/resolv.conf` file and the upstream DNS servers.
  +=====
   
   .Procedure
   
  
positive.code:       upstreams:
          - 3.3.3.3
          - 4.4.4.4:5454
  ----
  <1> `name` must comply with the `rfc6335` service name syntax.
  <2> `zones` must conform to the definition of a `subdomain` in `rfc1123`. The cluster domain, `cluster.local`, is an invalid `subdomain` for `zones`.
  <3> A maximum of 15 `upstreams` is allowed per `forwardPlugin`.
  +
  [NOTE]
  ====
  
negative.code: $ oc edit dns.operator/default
  ----
  +
  This allows the Operator to create and update the ConfigMap named `dns-default` with additional server configuration blocks based on `Server`. If none of the servers has a zone that matches the query, then name resolution falls back to the upstream DNS servers.
  +
  .Sample DNS
  [source,yaml]
  