Login Server Port unavailable

[cmoore20]

Hey guys, using:

[LoginServer]
Host=eqemulator.net:5998

Having weird issues, fired up wireshark, see that the destination host port is unavailable.

just thought I would post it

[cmoore20]

>ping 216.59.33.136

Pinging 216.59.33.136 with 32 bytes of data:

Reply from 216.59.33.136: bytes=32 time=54ms TTL=54
Reply from 216.59.33.136: bytes=32 time=45ms TTL=54
Reply from 216.59.33.136: bytes=32 time=47ms TTL=54
Reply from 216.59.33.136: bytes=32 time=45ms TTL=54

Also edit

I am seeing that your edge node, is the one responding with port unavailable:

9 52 ms 50 ms 50 ms er1-tengig-4-0-0.avl01.netriplex.com [66.219.27.6]

[Rogean]

flush dns try again, dns records didn't copy over correctly to new nameserver.. the ip your getting is the new server but its premature.

[Tudj]

Hey I am having an issue also trying to log in. Just says check internet connection, but all is well here.

[cmoore20]

What he was saying is that DNS was not updated to the new correct IP address. Sometimes, even if you flush your local DNS records, the nameserver for your ISP will still have the old IP cached since it has not had to check the authoritative nameserver for the zone for the update IP address..

There would be nothing you could do if your ISP's nameserver had the old IP cached unless you specifically pointed your DNS querry at a different server hoping it has the correct/new ip address, or they listed the new ip address on the forums.

at least i think so?

[Tudj]

Ok, so instead of having eqemulator.net:5998 in the eqhost.txt could you put it in as:

"correct ip":5998

?

[cmoore20]

Simple answer, yess... long answer no.

Doing a nslookup on the authorative nameserver, I think it is go daddy


Server: NS1.ROGEAN.COM
Address: 216.59.33.135

Name: eqemulator.net
Address: 64.120.211.247

The problem with specifying a IP address instead of a domain name would be if the login server moved, it would break your client again. A DNS entry is basically a virtual IP address, where administrators can edit where it points, so the clients do not have to.

A more stateful approach to high availability would be to have the DNS entry point at a VIP, and then be able to add/remove login servers from load at the administrators ease. This would be better than simply just changing the ip address associate with the domain name because the name servers would still be resolving requests to the VIP. However, this costs money to implement, and I think that emu might not have those kind of funds laying around.

[Tudj]

WOW! you rock Cmoore20, IP worked! Will change back when resolved.

eqhost.txt:

[LoginServer]
Host=64.120.211.247:5998