infra-docs-fpo/modules/sysadmin_guide/pages/unbound.adoc

= Fedora Infra Unbound Notes

Sometimes, especially after updates/reboots you will see alerts like
this:

....
18:46:55 < zodbot> PROBLEM - unbound-tummy01.fedoraproject.org/Unbound 443/tcp is WARNING: DNS WARNING - 0.037 seconds response time (dig returned an error status) (noc01)
18:51:06 < zodbot> PROBLEM - unbound-tummy01.fedoraproject.org/Unbound 80/tcp is WARNING: DNS WARNING - 0.035 seconds response time (dig returned an error status) (noc01)
....

To correct this, restart unbound on the relevant node (in the example
case above, _unbound-tummy01_), by running the `restart_unbound` Ansible
playbook from _batcave01_:

....
sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/restart_unbound.yml --extra-vars="target=unbound-tummy01.fedoraproject.org"
....
Added the infra SOPs ported to asciidoc. 2021-07-26 10:39:47 +02:00			`= Fedora Infra Unbound Notes`

			`Sometimes, especially after updates/reboots you will see alerts like`
			`this:`

			`....`
			`18:46:55 < zodbot> PROBLEM - unbound-tummy01.fedoraproject.org/Unbound 443/tcp is WARNING: DNS WARNING - 0.037 seconds response time (dig returned an error status) (noc01)`
			`18:51:06 < zodbot> PROBLEM - unbound-tummy01.fedoraproject.org/Unbound 80/tcp is WARNING: DNS WARNING - 0.035 seconds response time (dig returned an error status) (noc01)`
			`....`

			`To correct this, restart unbound on the relevant node (in the example`
Review unbound SOP Signed-off-by: Michal Konečný <mkonecny@redhat.com> 2021-09-10 16:00:40 +02:00			case above, _unbound-tummy01_), by running the `restart_unbound` Ansible
			`playbook from _batcave01_:`
Added the infra SOPs ported to asciidoc. 2021-07-26 10:39:47 +02:00
			`....`
			`sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/restart_unbound.yml --extra-vars="target=unbound-tummy01.fedoraproject.org"`
			`....`