search

pangea-project / pangea-kitchen

0 stars 1 forks source link

Resolving to monitoring.pangea.pub doesn't work #2

Closed bhush9 closed 6 years ago

bhush9 commented 6 years ago

https://github.com/blue-systems/pangea-kitchen/blob/ff89e83ef5ff7ab364cf5a93d7ec32c3cfaa95a2/site-cookbooks/nameserver/templates/default/named.conf.local#L8-L13

This doesn't really work

root@do-builder-series-b-001---16:~# ping monitoring.pangea.pub
ping: unknown host monitoring.pangea.pub
root@do-builder-series-b-001---16:~# nslookup monitoring.pangea.pub
Server:         10.135.69.54
Address:        10.135.69.54#53

** server can't find monitoring.pangea.pub: NXDOMAIN
root@do-builder-series-b-001---16:~# nslookup monitoring.pangea.pub 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   monitoring.pangea.pub
Address: 46.101.149.170

Causing do-builders, neon builder and few others to not talk with monitoring.pangea.pub and then spam monitoring channel with false alarms.

bhush9 commented 6 years ago

Interesting is despite having Google DNS as 2nd entry in /etc/resolv.conf it doesn't fallback to it? I guess something is wrong with resolvconf?

hsitter commented 6 years ago

It only falls back to secondary servers if the first server doesnt respond or if it says it doesn't recurse. Otherwise it assumes the server made all attempts to resolve the name and still came back empty handed.

In any event I couldn't make forwarding work for some reason, so I've reverted back to the original rule which recurses monitoring. into the external DNS to produce a result. we'll just have to live with the AAAA noise, which I think is a problem with the public DNS setup of this one subdomain.