Agentless, cloud-native backup for Amazon Web Services (AWS)
Post Reply
netwichi
Influencer
Posts: 10
Liked: never
Joined: Oct 15, 2024 9:15 am
Contact:

Communication requirements for VB4AWS and Route53

Post by netwichi »

VB4AWS has the following communication requirements:

(From)Backup Server (To)Route 53 Resolver (Protocol) UDP (Port)53
(From)Woker Instance (To)Route 53 Resolver UDP (Port)53
Default port required to perform DNS resolution if you plan to use a custom DNS server for your VPC.

When VB4AWS and Worker communicate with Route53, where do they perform name resolution?

I would like to know what servers and components VB4AWS and Worker need to be able to resolve names.
Mildur
Product Manager
Posts: 9846
Liked: 2603 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Communication requirements for VB4AWS and Route53

Post by Mildur »

Hello Netwichi

Then the backup appliance/worker instance is trying to resolve the name. I'm not sure how I can help you by telling which server (I can't open your box.com link). Backup appliances and worker instances are unique to each customer's environment.

The backup appliance is the machine you deployed initially:
- Deploying Backup Appliance

The workers are the machines that processes backup jobs:
Managing Worker Instances

Best,
Fabian
Product Management Analyst @ Veeam Software
Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests