Re: CNAME restrictions

2020-08-10 Thread Reindl Harald
Am 04.08.20 um 19:34 schrieb Matus UHLAR - fantomas: > On 04.08.20 17:29, Leroy Tennison wrote: >> I have a situation where, due to the system's location (IP subnet), >> its DNS >> name is ..datavoiceint.com.  We have a >> certificate for *.datavoiceint.com which we prefer to use > > wildcard in

Re: CNAME restrictions

2020-08-04 Thread Leroy Tennison
Thank you, -d surfaced the issue - now to decide what to do about it... From: bind-users on behalf of Kevin Darcy Sent: Tuesday, August 4, 2020 3:28 PM To: bind-users@lists.isc.org Subject: [EXTERNAL] Re: CNAME restrictions CAUTION: This email originated

Re: CNAME restrictions

2020-08-04 Thread Kevin Darcy
[ Classification Level: GENERAL BUSINESS ] Offhand, it looks like the server side is configured to only allow authenticated updates, but you're sending an unauthenticated one. A more nuanced issue might be if the ID you're running the nsupdate as, can't read the key files, so even though you may

Re: CNAME restrictions

2020-08-04 Thread Matus UHLAR - fantomas
On 04.08.20 17:29, Leroy Tennison wrote: I have a situation where, due to the system's location (IP subnet), its DNS name is ..datavoiceint.com. We have a certificate for *.datavoiceint.com which we prefer to use wildcard in certificates only covers one level of subdomains, so *.datavoiceint.c