URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround: verify dnsmasq status on bastion - may need to stop named and restart dnsmasq.

Description: Symptom - workstation and servera could not resolve imap.lab.example.com during the GE smtp sendonly exercise.

Root cause - on bastion, dnsmasq was failed, port already in use.

Fix - On bastion, stop named, restart dnsmasq.

Additional info:

The student had to step away early the day before. Most likely he had not done all the lab finish scripts from earlier chapters. I am guessing that one of those earlier lab scripts configures named on bastion.

The smtp-sendonly-start.yml playbook configures additional dnsmasq settings and restarts dnsmasq. This task is successful even though the service fails to load since the port was in use.