You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement a local DNS proxy for VPC/Underlay networks by:
Forward DNS requests from VPC/Underlay LSPs to the local OVS bridge br-int;
Run a DaemonSet that forwards the requests to the kube-dns service (/etc/resolv.conf).
To achieve this goal, we need to:
Add some extra ovn/ovs flows to store the ofport number into the destination mac and output the packet to br-int;
Implement a DNS proxy server that receives raw packets from br-int, forwards the requests to the upstream dns server and writes raw response packets to br-int.
Add some extra ovn/ovs flows to read ofport number from the source mac and output the packet to the request port.
Here is an example:
OVS datapath receives a DNS request from an OVS port with ofport number 1;
OVS datapath stores the ofport number into the packet's destination mac and the new destination mac would be ff:ff:ff:ff:00:01;
OVS datapath forwards the modified packet to the br-int port;
The DNS proxy server receives the raw packet from br-int and forwards the DNS request to the upstream server;
The DNS proxy server construct a raw response packet where the source mac is ff:ff:ff:ff:00:01;
The DNS proxy server sends the response packet to br-int;
OVS datapath receives the response packet from br-int and reads ofport number from the source mac;
OVS datapath forwards the response packet to OVS port with ofport number 1.
Who will benefit from this feature?
In clusters where kube-dns service is running in an overlay subnet, underlay subnets MUST turn on u2oInterconnection to access the DNS service.
For VPC networks, we have VPC DNS but it has some limitations:
It requires multus-cni and is kind of complicated to use;
Each VPC requires a CoreDNS deployment.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Description
Implement a local DNS proxy for VPC/Underlay networks by:
br-int
;kube-dns
service (/etc/resolv.conf).To achieve this goal, we need to:
br-int
;br-int
, forwards the requests to the upstream dns server and writes raw response packets tobr-int
.Here is an example:
ff:ff:ff:ff:00:01
;br-int
port;br-int
and forwards the DNS request to the upstream server;ff:ff:ff:ff:00:01
;br-int
;br-int
and reads ofport number from the source mac;Who will benefit from this feature?
In clusters where
kube-dns
service is running in an overlay subnet, underlay subnets MUST turn onu2oInterconnection
to access the DNS service.For VPC networks, we have VPC DNS but it has some limitations:
Anything else?
No response
The text was updated successfully, but these errors were encountered: