Agentless, cloud-native backup for Amazon Web Services (AWS)
Post Reply
mschwarzer
Influencer
Posts: 14
Liked: 1 time
Joined: Oct 22, 2018 8:31 am
Full Name: Michael Schwarzer
Contact:

vb4aws using custom dns

Post by mschwarzer »

Hello @ll,

we implement vb4aws and all is working fine. But because of some larger windows enrollment in vpc we try to switch from using aws dns to customers environment using the dhcp option groups. Things weren't that easy, how you can imagine. The route 53 resolver is not easy to troubleshoot and customer refuses to operate this. After all dns registration, foreward and backward resolution for the worker appliances are not all the way. The private aws dns names we solved with a conditional foreward and instance-data we tried to solve with an matching dns entry.
After that the 'worker-up' event is still not catched and the only missing part seems 'instance-data'. It looks like the dns query from worker was answerred from the customes dns with 'NXRECORD' because of the missing search domain, neither ec2.internal nor dhcp provided dns search domain

Do you have any hint fro me to look at and are there experiances regarding this or is there some general mistake in thinking on my side?

Best regards,
Michael
nielsengelen
Product Manager
Posts: 5619
Liked: 1177 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: vb4aws using custom dns

Post by nielsengelen »

Hi Michael,

Just to clarify so I can potentially help you (if this can work at all), the worker is causing issues when you do a backup or restore because of the custom DNS?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
mschwarzer
Influencer
Posts: 14
Liked: 1 time
Joined: Oct 22, 2018 8:31 am
Full Name: Michael Schwarzer
Contact:

Re: vb4aws using custom dns

Post by mschwarzer »

Hi,
as soon as we switch the dhcp-option group to point to the customer dns the worker appliance is not recognized as 'running' and the flr-test failes.
I have worked through the VBA-Worker-cloud-init.log and all looks good while using the correct search domain. But once the worker appl. is querying the customer dns for 'unqualified' instance-data (found this in the dns logs) the answer from dns is 'NXDOMAIN and the test fails.
I'm still a little confused about this call can even happen.
nielsengelen
Product Manager
Posts: 5619
Liked: 1177 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: vb4aws using custom dns

Post by nielsengelen »

Hi Michael, I would suggest opening a support case for insight here and maybe they have a workaround or solution for this. Can u let me know the case ID once done?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests