starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #1228] [Feature Request] Create DNS record automatically #1000

New issue

Closed

opened 2026-02-26 06:35:23 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:35:23 +03:00

Owner

Originally created by @jeremy-chua on GitHub (Jul 9, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1228

It will be great to have this feature to automatically create a DNS record to the domain provider when adding a proxy host.

The Certificates DNS Challenger already supports a vast range of DNS providers. Having the above feature won't be a big issue... i suppose. :)

Originally created by @jeremy-chua on GitHub (Jul 9, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1228 It will be great to have this feature to automatically create a DNS record to the domain provider when adding a proxy host. The Certificates DNS Challenger already supports a vast range of DNS providers. Having the above feature won't be a big issue... i suppose. :)

kerem

2026-02-26 06:35:23 +03:00

closed this issue
added the
enhancement

stale

help wanted
labels

kerem commented

2026-02-26 06:35:23 +03:00

Author

Owner

@the1ts commented on GitHub (Jul 29, 2021):

I can see this being way more complex than at first sight. What if there is a different A-record? Update or not?, what if there is a c-name already, update or not? Removing can be tricky, if its been manually changed do we leave or remove?

If you are looking for an easy solution to the home server problem, do what many do for home use, make a wildcard DNS entry pointing to home, then you only need specific DNS to override that wildcard IP for things not on your home IP. Leaving you the ability to make up hostnames in your home NPM on the fly that will work immediately for SSL creation and in your web browser.

@the1ts commented on GitHub (Jul 29, 2021): I can see this being way more complex than at first sight. What if there is a different A-record? Update or not?, what if there is a c-name already, update or not? Removing can be tricky, if its been manually changed do we leave or remove? If you are looking for an easy solution to the home server problem, do what many do for home use, make a wildcard DNS entry pointing to home, then you only need specific DNS to override that wildcard IP for things not on your home IP. Leaving you the ability to make up hostnames in your home NPM on the fly that will work immediately for SSL creation and in your web browser.

kerem commented

2026-02-26 06:35:23 +03:00

Author

Owner

@jeremy-chua commented on GitHub (Jul 30, 2021):

Thanks!
Works like a charm.

@jeremy-chua commented on GitHub (Jul 30, 2021): Thanks! Works like a charm.

kerem commented

2026-02-26 06:35:23 +03:00

Author

Owner

@chaptergy commented on GitHub (Oct 5, 2021):

The DNS challenge is performed by certbot, a library by the organization behind LetsEncrypt. So re-implementing all the logic for DNS record creation would be a huge untertaking and would lead once again to lots of requests to add support for a very specific provider. So unless someone from the community would want to spend his time implementing this, I don't think it is likely to be added.

@chaptergy commented on GitHub (Oct 5, 2021): The DNS challenge is performed by [certbot](https://certbot.eff.org/), a library by the organization behind LetsEncrypt. So re-implementing all the logic for DNS record creation would be a huge untertaking and would lead once again to lots of requests to add support for a very specific provider. So unless someone from the community would want to spend his time implementing this, I don't think it is likely to be added.

kerem commented

2026-02-26 06:35:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 8, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 8, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:35:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 20, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 07:33:54 +03:00

[GH-ISSUE #3029] Issue 1000 open - ssl cert via ddns not auto updating (I should get a prize for creating issue #1000 open !) #2066

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1000

No description provided.

Rows
Columns