# NTS Support in the pools

**URL:** https://community.ntppool.org/t/nts-support-in-the-pools/2939
**Category:** Server operators
**Created:** [July 13, 2023, 12:00pm UTC](https://community.ntppool.org/t/nts-support-in-the-pools/2939 "2023-07-13T12:00:37Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![alica](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/alica/32/337_2.png) [@alica](https://community.ntppool.org/u/alica)
#### Post date: [July 14, 2023, 8:40am UTC](https://community.ntppool.org/t/nts-support-in-the-pools/2939/2 "2023-07-14T08:40:39Z")

</div>

There were some discussion in the past, but no progress until now.

> [@Proper cn in certificate for use with NTS](https://community.ntppool.org/t/proper-cn-in-certificate-for-use-with-nts/1381):
>
> I’m tinkering with NTS on 188.166.95.178 and 193.175.73.151 – NTS seems to be working, but which cn (in the x.509 Certificate) should pool servers use? Turns out that both servers can properly communicate using [char-ntp-pool.charite.de](http://char-ntp-pool.charite.de) and [mail.python.org](http://mail.python.org): server char-ntp-pool.charite.de nts iburst server mail.python.org nts iburst

---

_[View the full topic](https://community.ntppool.org/t/nts-support-in-the-pools/2939)._
