Closed Bug 1491497 Opened 6 years ago Closed 6 years ago

Make sure we are using proper DNS resolvers in AWS

Categories

(Release Engineering :: General, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rail, Unassigned)

Details

Filing hopefully only for posterity. Today I discovered that some of the balrogworkers (and later some other scriptworkers) stopped picking up tasks from the queue. After some investigations I realized that they were using SCL3 nameservers. Those are coming from DHCP from AWS (use1 DHCP options: https://console.aws.amazon.com/vpc/home?region=us-east-1#dhcpOptions:filter=dopt-ef162084). After manually editing /etc/resolv.conf I added a new DHCP option set wit the following nameaservers: 10.50.75.120 10.50.75.121 10.50.75.123 and applied it to the VPC in use1 and usw2. After rebooting a couple of scriptworkers, I verified that they worked fine. I copied those IPs from my resolv.conf, so I'm not 100% sure they are correct or maybe we want to use different nameservers in different regions.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.