DNSSEC questionTopic: DNSSEC question
my domain has both DS and TLSA recordsI am thinking the TLSA records in my domain are for the dynu public certificate hash._443._tcp.dynu.com. IN TLSA 3 1 1 ( ba60893bb982d1d2aff77e65a61146f3add61129da75ff85a483114476c1 8854)The way I am expecting the trust chain to work is:1: Dynu receives DS record from domain2: Dynu verifies TLSA record with self signed certificate I entered.3: My domain looks for dynu public certificate and matches it to TLSA 4: Trust chain complete - domain has TLSA match from dynu "and" dynu has a TLSA match from domain.Not working...http works https does not.Any help is greatly appreciatedThank you
Reply with quote | Report
Found issueIp I connect the domain to is not secure.162.216.242.206Doan anyone know a secure way past this?
Reply with quote | Report
| Author | Topic: DNSSEC question |
|---|---|
|
wealthyforever33 Joined: 21/02/2022 
|
DNSSEC questiondimanche 13 mars 2022 20:26
my domain has both DS and TLSA recordsI am thinking the TLSA records in my domain are for the dynu public certificate hash._443._tcp.dynu.com. IN TLSA 3 1 1 ( ba60893bb982d1d2aff77e65a61146f3add61129da75ff85a483114476c1 8854)The way I am expecting the trust chain to work is:1: Dynu receives DS record from domain2: Dynu verifies TLSA record with self signed certificate I entered.3: My domain looks for dynu public certificate and matches it to TLSA 4: Trust chain complete - domain has TLSA match from dynu "and" dynu has a TLSA match from domain.Not working...http works https does not.Any help is greatly appreciatedThank you
|
|
wealthyforever33 Joined: 21/02/2022
|
DNSSEC question dimanche 13 mars 2022 20:46
ADDED note: I am using url redirect to wix
|
|
wealthyforever33 Joined: 21/02/2022
|
DNSSEC question lundi 14 mars 2022 08:24
Found issueIp I connect the domain to is not secure.162.216.242.206Doan anyone know a secure way past this?
|
It is currently samedi 23 novembre 2024 20:38 US Mountain Standard Time
samedi 23 novembre 2024 20:38