Page 1 of 1

[BUG] LoginServer.ini cannot use FQDN

Posted: Tue May 06, 2008 5:37 pm
by John Adams
Can you change it so we can use more than just our IP address(es) for the local system locations? My World machine, for instance, is on 10.1.1.1 (for example) but locally it's fully qualified domain name is "everquest2.emulators.local" and I am getting truncated - I think - when the world starts.
With IP, it the console looks like this:

Code: Select all

World server listening on: 10.1.1.1:9200
With FQDN, it looks more like:

Code: Select all

World server listening on: everquest2.emul:9200
Those of us who actually know how to set up DNS would like to be able to cash in on that whole "dynamic" thingy. ;) Unless this is just a display bug at the console, then something else might be wrong.
Thanks!
-J

Posted: Tue May 06, 2008 9:00 pm
by ichijin
whatismyip.org
It will give you something like: 224.12.212.21
Use that as your external IP. If your eqemu2.blahblah.com is 'bound' to 224.12.212.21 it will work just the same.

Posted: Tue May 06, 2008 9:26 pm
by LethalEncounter
Sure, I'll take a look at it. I believe that is one of the pieces of code from EQEmu, so your guess is as good as mine about it :P Everything is hazy from back then.

Posted: Wed May 07, 2008 10:38 am
by John Adams
Thanks, Ichi. I know what my IP is lol...
This is about address translation and DNS behind my firewall. I move machines around a lot (IPs) but generally the FQDN stays the same.
LE, I found out after (thanks to link2009's persistence to check my ports heh) that my initial problem here *might* have been a DHCP failure on my part. Let me re-test this when I get home, and maybe if anything the truncated text is simply a visual problem. Cuz I use FQDN for all other emulators, including EQEmu... so if this is leftover code, it's likely working fine.

Posted: Sat May 10, 2008 10:50 am
by John Adams
Just re-tested this using my local FQDN (server.domain.com) and the name does not resolve. I definitely need to use an IP address, which is not really good for those who move things around a lot (like me heh).
But seeing as how most people will not re-IP things regularly, I'd say it was pretty low-priority in the grand scope of things. I can take a look through the code sometime to see if there is some character length limitation on reading that field or not. I think even I am capable of changing that, if I need to.

Posted: Wed May 14, 2008 4:07 pm
by LethalEncounter
You can use your a cname (domain name) for worldaddress, but not for internalworldaddress. For internalworldaddress you must specify a valid local IP address. It can be changed if necessary, but obviously it isnt a priority.