# Hall notification module? **URL:** \ **Category:** Get Help\ **Tags:** module\ **Created:** [March 11, 2024, 2:50pm UTC](https://forum.ansible.com/t/hall-notification-module/4321 "2024-03-11T14:50:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jpmens](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jpmens/32/5543_2.png) [@jpmens](https://forum.ansible.com/u/jpmens)\ **Post date:** [March 11, 2024, 2:50pm UTC](https://forum.ansible.com/t/hall-notification-module/4321/1 "2024-03-11T14:50:18Z")
Glancing at the list of notification modules I notice [hall](https://docs.ansible.com/ansible/2.8/modules/hall_module.html). Out of curiousity I attempt to reach `hall.com` which is dead: ```auto ; EDE: 20 (Not Authoritative) ; EDE: 22 (No Reachable Authority): (at delegation hall.com.) ; EDE: 23 (Network Error): (149.112.161.1:53 rcode=REFUSED for hall.com A) ``` It’s parent name servers don’t respond for the zone. Is there any reason to keep this module if the messaging API it uses is no longer available? What’s the procedure to deprecate such a module? ---
**Author:** ![jpmens](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jpmens/32/5543_2.png) [@jpmens](https://forum.ansible.com/u/jpmens)\ **Post date:** [March 11, 2024, 2:59pm UTC](https://forum.ansible.com/t/hall-notification-module/4321/2 "2024-03-11T14:59:59Z")
And this serves me right for reading outdated docs. Pardon the noise: `hall` no longer exists. ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [April 10, 2024, 3:00pm UTC](https://forum.ansible.com/t/hall-notification-module/4321/3 "2024-04-10T15:00:39Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.