For people with dynamic IPs, free services like http://www.dyndns.com exist.
I would prefer to even make these domain names standardized. So that each server is accessed by something like alfa052.dyndns.com, alfa004.dyndns.com, etc.
This gives us some advantages on a few fronts, but I'd like to hear any reasons hosters may not want to do this, and if they have any dynamic domain name service they prefer.
Possible requirement: domain names for servers.
That may have been affected by the .net .org issue, but I thought it still worked :)
PC: Bot (WD)
Code: Select all
----- ----- ----- -----
/ \ / \ / \ / \
/ RIP \ / RIP \ / RIP \ / RIP \ /
| | | | | | | | |
*| * * |* *| * * |* *| * * |* *| * * |* *|
_)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_(Not sure, that was before my time here.
If Bool or Infra or whomever wants to set up a DNS and do that, thats fine with me. Not sure how hard it is to set up things like that. But baring that, I think one of the many free services out there should be considered.
So I take it no one has any objections for this to be a requirement? And when I say requirement, I mean like things in-game could break without it.
If Bool or Infra or whomever wants to set up a DNS and do that, thats fine with me. Not sure how hard it is to set up things like that. But baring that, I think one of the many free services out there should be considered.
So I take it no one has any objections for this to be a requirement? And when I say requirement, I mean like things in-game could break without it.
We are paying for alandfarway.org. We are hosting a webserver (and hopefully SSH/FTP at some point). I see no reason to use an external resource to do what our webserver can easily do.
Bool - correct me if I'm wrong, but maintaining an ACL or some such to redirect alfa_103.%TLD% to %103_IP_ADDRESS% is trivial, yes? From there, we only need a webform to allow HDMs to update the IP. It would be nice to have an app that automatically updated the webform on server reboot (ala DynDNS), but not a hard requirement.
Bool - correct me if I'm wrong, but maintaining an ACL or some such to redirect alfa_103.%TLD% to %103_IP_ADDRESS% is trivial, yes? From there, we only need a webform to allow HDMs to update the IP. It would be nice to have an app that automatically updated the webform on server reboot (ala DynDNS), but not a hard requirement.
PC: Bot (WD)
Code: Select all
----- ----- ----- -----
/ \ / \ / \ / \
/ RIP \ / RIP \ / RIP \ / RIP \ /
| | | | | | | | |
*| * * |* *| * * |* *| * * |* *| * * |* *|
_)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_(I'd imagine there is some open-source software to occomplish this, and our web site seems to run on a *nix OS. In any case, I'd say this IS a hard requirement. People don't update their DM times, so I don't expect them to update their IPs, especially if dynamic.Fionn wrote:It would be nice to have an app that automatically updated the webform on server reboot (ala DynDNS), but not a hard requirement.
I'd rather use a free service over ALFA's if Bool doesn't want to provide this. Actually I'd rather use a free service for some other reasons as well (such as Bool leaving and alfa.org switching over to a windows box), but I agree domain names like 052.alandfaraway.org would be nice, easy to remember, and professional-looking.
The alfa_xxx.alandfaraway.org system still exists for possible use (and has since well before NWN was even released).
The main reasons it seems to no longer be used however, is things like DungeonServer, which has dynamic IPs and no possibility of a DynDNS type service, or servers simply not updating or publishing their IP.
HDMs have their own section on the ALFA website where they can update their Server's IP address.
(Note: This used to update the Domain automatically, but is currently not - until we get the ACR changed from alfa_xxx. to just alfaxxx. - so whenever it has been updated, I just make the change manually.)
The main reasons it seems to no longer be used however, is things like DungeonServer, which has dynamic IPs and no possibility of a DynDNS type service, or servers simply not updating or publishing their IP.
HDMs have their own section on the ALFA website where they can update their Server's IP address.
(Note: This used to update the Domain automatically, but is currently not - until we get the ACR changed from alfa_xxx. to just alfaxxx. - so whenever it has been updated, I just make the change manually.)
OK, talked with Bool a bit. We can just continue to use ALFA's DNS service, and require hosters enter a valid static IP or URL. So hosters can use whatever dyndns service they want, or none if their IP is static. To the player and the portalling scripts the effect should be seamless, alfaXXX.alandfaraway.org should always point to the right server.
Until Bool pointed it out, I stupidly did not think of the possibility of using ALFA's DNS to route to a URL of a dyndns service
Until Bool pointed it out, I stupidly did not think of the possibility of using ALFA's DNS to route to a URL of a dyndns service
What are the qualifications of the TA again?Ronan wrote:Until Bool pointed it out, I stupidly did not think of the possibility of using ALFA's DNS to route to a URL of a dyndns service
njub
PC: Bot (WD)
Code: Select all
----- ----- ----- -----
/ \ / \ / \ / \
/ RIP \ / RIP \ / RIP \ / RIP \ /
| | | | | | | | |
*| * * |* *| * * |* *| * * |* *| * * |* *|
_)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_//(/|_)(__)/\\_(