You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ziti-router: If you modify/delete an existing service with wildcard DNS the intercept is deleted but not reinserted for any previously queried hostnames
#1440
Closed
r-caamano opened this issue
Apr 4, 2023
· 2 comments
· Fixed by #1719
ziti-router: The first time you modify/delete an existing service with a wildcard dns as the intercept i.e. add or remove ports then the associated tproxy rule will be deleted and not re-added for any previously queried addresses. After querying a new host associated with the wildcard domain name tproxy entries are created, however they map to the previous tproxy port and not new tproxy listening port associated with the modified service. Also subsequent modifications to the same service no longer modify any tproxy entries. If you then try to delete the service, the tproxy rule is not deleted and subsequently not properly recreated if a new service is added with the same wildcard url. This issue is not cleared unless the ziti-router process is restarted.
The text was updated successfully, but these errors were encountered:
r-caamano
changed the title
ziti-router: If you modify an existing service with wildcard DNS the intercept is deleted but not reinserted for any previously queried hostnames
ziti-router: If you modify/delete an existing service with wildcard DNS the intercept is deleted but not reinserted for any previously queried hostnames
Apr 4, 2023
ziti-router: The first time you modify/delete an existing service with a wildcard dns as the intercept i.e. add or remove ports then the associated tproxy rule will be deleted and not re-added for any previously queried addresses. After querying a new host associated with the wildcard domain name tproxy entries are created, however they map to the previous tproxy port and not new tproxy listening port associated with the modified service. Also subsequent modifications to the same service no longer modify any tproxy entries. If you then try to delete the service, the tproxy rule is not deleted and subsequently not properly recreated if a new service is added with the same wildcard url. This issue is not cleared unless the ziti-router process is restarted.
The text was updated successfully, but these errors were encountered: