[GH-ISSUE #145] Custom domains hosting #137

New issue

Closed

opened 2026-02-26 09:36:00 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:36:00 +03:00

Owner

Originally created by @ghost on GitHub (Apr 16, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/145

We should be able to add our own domain name and manage it directly in nsupdate-info.
Now we are only able to update another nameserver through nsupdate-info.

Originally created by @ghost on GitHub (Apr 16, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/145 We should be able to add our own domain name and manage it directly in nsupdate-info. Now we are only able to update another nameserver through nsupdate-info.

kerem

2026-02-26 09:36:00 +03:00

closed this issue
added the
enhancement

needs help

security
labels

kerem commented

2026-02-26 09:36:01 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Apr 27, 2014):

This would require dynamically updating our nameserver with new zones (like owndomain.com).
Not sure about the security implications of this, needs evaluation.

Also, usually one wants 2 nameservers for a domain...

@ThomasWaldmann commented on GitHub (Apr 27, 2014): This would require dynamically updating our nameserver with new zones (like owndomain.com). Not sure about the security implications of this, needs evaluation. Also, usually one wants 2 nameservers for a domain...

kerem commented

2026-02-26 09:36:01 +03:00

Author

Owner

@elnappo commented on GitHub (Dec 28, 2014):

What is your use case? Do you want to add a subdomain for dydns (dyn.example.com?) and set an NS record to nsupdate.info nameserver?

@elnappo commented on GitHub (Dec 28, 2014): What is your use case? Do you want to add a subdomain for dydns (dyn.example.com?) and set an NS record to nsupdate.info nameserver?

kerem commented

2026-02-26 09:36:01 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 14, 2015):

Note: this does not only need adding a new domain to the nameserver (that could be done automatically maybe), but also might need adding bind (nameserver specific) configuration, like:

allow/deny rules what in the zone may be updated
new key for dynamic updates of the zone

So, I fear this is getting a bit complicated / out of scope of the project (it's not a frontend to create nameserver-specific configuration) and thus I am closing this as "won't fix".

In general: if someone has a cool domain and wants to donate it for a longer period of time, we can always setup something manually on our DNS servers.

@ThomasWaldmann commented on GitHub (Feb 14, 2015): Note: this does not only need adding a new domain to the nameserver (that could be done automatically maybe), but also might need adding bind (nameserver specific) configuration, like: - allow/deny rules what in the zone may be updated - new key for dynamic updates of the zone So, I fear this is getting a bit complicated / out of scope of the project (it's not a frontend to create nameserver-specific configuration) and thus I am closing this as "won't fix". In general: if someone has a cool domain and wants to donate it for a longer period of time, we can always setup something manually on our DNS servers.