it has nothing to do with lag and fixing the reverse dns will not fix lag... it's just naming convention
DNS stands for Domain Name Service
It's what ties a domain/server name to a given IP
gls.ddo.com is tied to
192.252.160.23 198.252.160.23 ( see below ) since the change before that it was tied to another IP address.
There's several types of records that belongs to various usage in the name resolution :
you can get the full list here :
https://tools.ietf.org/html/rfc1035 and here :
https://tools.ietf.org/html/rfc1034 and learn a lot about DNS along the way )
When you play with nslookup you can get things like that :
------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
ddo.com, type = A, class = IN
ANSWERS:
-> ddo.com
internet address = 198.252.160.57
ttl = 1800 (30 mins)
------------
Réponse ne faisant pas autorité :
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
ddo.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> ddo.com
ttl = 1800 (30 mins)
primary name server = ns01.ddo.com
responsible mail addr = root.ddo.com
serial = 2102003109
refresh = 300 (5 mins)
retry = 900 (15 mins)
expire = 2419200 (28 days)
default TTL = 10800 (3 hours)
------------
Nom : ddo.com
Address: 198.252.160.57
I asked for the IP of the host named ddo.com
nslookup told me that it's IP address is 198.252.160.57... which just told me that
I fucked up this morning...
as I typed 192.252.160.23 this morning, which gave me a wrong answer... That's what happens when you try to do network stuff before the morning coffee...
lets see now... I have set nslookup in debug mode, so it shows me the queries it's performing.
> 198.252.160.23
Serveur : dns-adsl-gpe2-a.wanadoo.fr
Address: 80.10.246.3
------------
Got answer:
HEADER:
opcode = QUERY, id = 6, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
23.160.252.198.in-addr.arpa, type = PTR, class = IN
AUTHORITY RECORDS:
-> 198.in-addr.arpa
ttl = 3600 (1 hour)
primary name server = z.arin.net
responsible mail addr = dns-ops.arin.net
serial = 2016031249
refresh = 1800 (30 mins)
retry = 900 (15 mins)
expire = 691200 (8 days)
default TTL = 10800 (3 hours)
------------
*** dns-adsl-gpe2-a.wanadoo.fr ne parvient pas ŕ trouver 198.252.160.23 : Non-existent domain
>
Well it's still fucked up, but not in the same way, it says that no domain is tied to the IP 198.252.160.23. ( NXDOMAIN )
So they didn't even bother to fill up the reverse records ( the PTR type )
Anyway, as I said it doesn't matter to players, only Luddite like me do revese DNS queries. DDO only needs the normal DNS records ( the A ones ) to work,
so having no PTR records doesn't matter.
For fun :
> set type=MX
> ddo.com
Serveur : dns-adsl-gpe2-a.wanadoo.fr
Address: 80.10.246.3
------------
Got answer:
HEADER:
opcode = QUERY, id = 9, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 3, authority records = 0, additional = 0
QUESTIONS:
ddo.com, type = MX, class = IN
ANSWERS:
-> ddo.com
MX preference = 20, mail exchanger = a.mx.turbine.com
ttl = 1800 (30 mins)
-> ddo.com
MX preference = 10, mail exchanger = ddo-com.mail.protection.outlook.com
ttl = 1800 (30 mins)
-> ddo.com
MX preference = 30, mail exchanger = b.mx.turbine.com
ttl = 1800 (30 mins)
------------
Réponse ne faisant pas autorité :
ddo.com
MX preference = 20, mail exchanger = a.mx.turbine.com
ttl = 1800 (30 mins)
ddo.com
MX preference = 10, mail exchanger = ddo-com.mail.protection.outlook.com
ttl = 1800 (30 mins)
ddo.com
MX preference = 30, mail exchanger = b.mx.turbine.com
ttl = 1800 (30 mins)
>
I asked nslookup to give me the mail servers. There's 3 mail servers belonging to Turbine.
Interestingly the middle one tells me a lot.
Turbine uses Outlook and they have an external access, where they can connect to with their laptops/mobile devices as if they were in the internal network .
We have the same thing at work ( sadly I despise Outlook, so I can't use that, and I have to fire up the VPN every time I want to check my emails )
It also tells me that they are probably using Outlook365 and the rest of the Microsoft rented suite...