# CNAME Replies Not Being Blocked

**URL:** <https://discourse.pi-hole.net/t/cname-replies-not-being-blocked/30917>\
**Category:** Beta 5.0\
**Created:** [April 22, 2020, 8:35pm UTC](https://discourse.pi-hole.net/t/cname-replies-not-being-blocked/30917 "2020-04-22T20:35:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pihole2](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/e5b9ba/32.png) [@pihole2](https://discourse.pi-hole.net/u/pihole2)\
**Post date:** [April 22, 2020, 8:35pm UTC](https://discourse.pi-hole.net/t/cname-replies-not-being-blocked/30917/1 "2020-04-22T20:35:53Z")

</div>

**Problem with Beta 5.0:**

I just updated to version 5.0 today. CNAME replies in the query log are not showing as being blocked. The A and AAA records are blocked but not the CNAME reply. Is this the expected behavior?

 ![Pi-Hole-CNAME](https://discourse.pi-hole.net/uploads/default/original/2X/8/88a445bb6036bd2158e1095b58aff9d0463a8420.png)

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [April 22, 2020, 8:39pm UTC](https://discourse.pi-hole.net/t/cname-replies-not-being-blocked/30917/2 "2020-04-22T20:39:26Z")

</div>

Let's take a look at your configuration. Please send us the token generated by

`pihole -d`

or do it through the Web interface:

_ **Tools \> Generate Debug Log** _

Between the two queries, did you whitelist the domain? It was blocked, then one minute later the same domain was not blocked.

---

<div class="post-metadata">

**Author:** ![pihole2](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/e5b9ba/32.png) [@pihole2](https://discourse.pi-hole.net/u/pihole2)\
**Post date:** [April 22, 2020, 8:57pm UTC](https://discourse.pi-hole.net/t/cname-replies-not-being-blocked/30917/3 "2020-04-22T20:57:47Z")

</div>

Thank you for the quick response/assistance. It must have happened when I moved the device to a new group. That group probably didn't have the blacklists applied anymore. I apologize for wasting time.