AVX and AWS DNS

AWS DNS Design Options (from reference #1) Option 1: Inbound and Outbound endpoints deployed in the hub vpc Option 2: Inbound and Outbound endpoints deployed in the hub vpc for forwarding Option 3: VPC sharing This option will not be investigated as it does not fit a scalable and secure hub and spoke topology. Option 4: Shared Private Zones and Forwarded Rules (AWS recommended) Testing Configuration Information Hosted Private Zone: Outbound Config: Rule: Inbound config: Design Option 1 Create a dhcp option set pointing to the inbound endpoints: and associate to the vpc: Servers will have its /etc/resolv.conf updated to: … Continue reading AVX and AWS DNS

Using a GCP LB to provide DNS High-Availability

DNS uses UDP port 53 for most of it operations but relies on TCP for operations that requires the transmission of packets exceeding 512 bytes. When the message size exceeds 512 bytes, it triggers a ‘TC’ bit (Truncation) in DNS to inform the client that the message length has exceeded the allowed size. The client needs then to re-transmit over TCP (size limit is 64000 bytes). Back End Configuration If you happen to run the HC across a device like routers or firewall you will need to configure DNAT for those devices to properly reply back to the HC of … Continue reading Using a GCP LB to provide DNS High-Availability