DNS resolution fails inside app (part 3)

1

We’re seeing another occurence of DNS resolution fails inside app (part 2) with machine e784961b297338:

Get "https://ola.prod.code.seat.cloud.vwgroup.com/v2/users/f9ae0043-fb86-4fb6-8709-8f28ba69ac15/vehicles/VSSZZZK1ZNP007453/mycar": dial tcp: lookup ola.prod.code.seat.cloud.vwgroup.com on [fdaa::3]:53: server misbehaving

@lillian wrote before:

Hi, we looked at this and found it was related to a DNSSEC configuration issue with our recursive DNS server. It should be working now.

@lillian could you kindly take another look?

Much appreciated, thank you!

2

@lillian would be great if you could check DNS resolver config once more- thank you!

3

This failed on a specific host. It’s possible the new config had not been properly reloaded on that one.

It’s now fixed. We’ll be adding a check and an alert for this issue.

2 Likes
4

Thanks @jerome.

It’s possible the new config had not been properly reloaded on that one.

For what it’s worth: it seems the machine id here is seeing this issue from time to time. Re-deploying does seem to fix it sometimes.

5

That’s odd. Is this still the case 4 days later?

6

Not observed since you‘ve fixed it. Will open another posting if it happens again.

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.