Page MenuHomePhabricator

dns-floating-ip-updater.py not working with 155.80.208.in-addr.arpa
Closed, InvalidPublic

Description

Running /etc/dns-floating-ip-updater.py on cloudcontrol1003 will output many warnings like these:

2018-11-13T15:05:00Z __main__     WARNING : Not handling 156.155.80.208.in-addr.arpa. because it doesn't end with 56.15.185.in-addr.arpa.
2018-11-13T15:05:00Z __main__     WARNING : Not handling 156.155.80.208.in-addr.arpa. because it doesn't end with 56.15.185.in-addr.arpa.
2018-11-13T15:05:00Z __main__     WARNING : Not handling 156.155.80.208.in-addr.arpa. because it doesn't end with 56.15.185.in-addr.arpa.
2018-11-13T15:05:00Z __main__     WARNING : Not handling 156.155.80.208.in-addr.arpa. because it doesn't end with 56.15.185.in-addr.arpa.
2018-11-13T15:05:00Z __main__     WARNING : Not handling 156.155.80.208.in-addr.arpa. because it doesn't end with 56.15.185.in-addr.arpa.

Practical impact is that reverse DNS entries for IPs in the 208.80.155 network are not created.

Event Timeline

<Krenair> There should be two instances of that cron running
<Krenair> One for each region
<Krenair> Each region should not touch records for the other region
<Krenair> So you should expect a *lot* of 'Not handling something.x because it doesn't end with y'

GTirloni triaged this task as Medium priority.

Change 473234 had a related patch set uploaded (by Andrew Bogott; owner: Andrew Bogott):
[operations/puppet@production] mwopenstackclients: select the designate endpoint for the proper region

https://gerrit.wikimedia.org/r/473234