(possibly dumb question) will changing my DNS screw anything up playing ED?

I am thinking of changing my DNA to 1.1.1.1 as its apparently more secure, but will this be likely to (negatively) effect anything ED wise?

thanks

(as i said, sorry if this this a really stupid question)
 

Brett C

Frontier
My DNS currently consists of the following, as per pfSense...

DNS server(s)
  • 127.0.0.1
  • 1.1.1.1
  • 1.0.0.1
  • 208.67.222.222
  • 208.67.220.220
  • 8.8.8.8
  • 8.8.4.4
I've had absolutely no issues using it while playing Elite.
 
I am thinking of changing my DNA to 1.1.1.1 as its apparently more secure, but will this be likely to (negatively) effect anything ED wise?

thanks

(as i said, sorry if this this a really stupid question)

It's not a stupid question at all. 1.1.1.1 is Cloudflare's new DNS service over https. Initial performance reviews of it suggest it's one of the fastest services out there and they claim not to sell usage data to third parties - seems like a no brainer to me. It won't affect your ED experience at all, so go for it. [up]
 
It might, AFAIK some routers still don't accept the new DNS (It is (or was some weeks ago) the case of Movistar here in Spain.) So first you should check if your internet provider does accept it.
 
My DNS currently consists of the following, as per pfSense...

DNS server(s)
  • 127.0.0.1
  • 1.1.1.1
  • 1.0.0.1
  • 208.67.222.222
  • 208.67.220.220
  • 8.8.8.8
  • 8.8.4.4
I've had absolutely no issues using it while playing Elite.

Something to note, 127.0.0.1 is not a DNS server but is LOCALHOST. Anything transmitted over that is only going to your own machine.
As for me, I am using the new 1,1,1,1 and 1,0,0,1 and have no issues with anything
 
Something to note, 127.0.0.1 is not a DNS server but is LOCALHOST. Anything transmitted over that is only going to your own machine.
As for me, I am using the new 1,1,1,1 and 1,0,0,1 and have no issues with anything

I'm guessing that Brett is running his own DNS server, in which case the inclusion of 127.0.0.1 is perfectly valid.
 
My DNS currently consists of the following, as per pfSense...

DNS server(s)
  • 127.0.0.1
  • 1.1.1.1
  • 1.0.0.1
  • 208.67.222.222
  • 208.67.220.220
  • 8.8.8.8
  • 8.8.4.4
I've had absolutely no issues using it while playing Elite.

Brett, did you just copy that from /etc/hosts?
 

Brett C

Frontier
Something to note, 127.0.0.1 is not a DNS server but is LOCALHOST. Anything transmitted over that is only going to your own machine.
As for me, I am using the new 1,1,1,1 and 1,0,0,1 and have no issues with anything

That's pfSense doing that for lan related stuff (internal/lan name resolving).
 
Oh, I was not saying anything against that at all. I figured you had your reasons for that on there. I just wanted to relate that to the rest who might not know what LOCALHOST is as an IP. I figured you had your reasons for using that. I know a few people who have their own local DNS on their systems. So my post was just meant to add a bit more information to those who did not know and answer the question from my own experience.
 

Brett C

Frontier
Perhaps it is a placebo effect but websurfing on my phone seems far snappier in jumping from one link to another even tho overall download bandwidth is the same since changing DNS to 1.1.1.1 in my router. I was using talktalk default settings. Sadly sick child meant my game night got cancelled so not gamed yet
 
XBone user here currently have Google (Public DNS) 8.8.8.8; 8.8.4.4 configured on the Xbox with a wired connection to my Plus.net Router.
Would I gain any benefit in reconfiguring to the suggested cloudfare DNS service ?

For IPv4: 1.1.1.1 and 1.0.0.1
For IPv6: 2606:4700:4700::1111 and 2606:4700:4700::1001 - [Not currently supported by Plus.net]

With what I currently have set now, Wings / Multi-Crew seem to be pretty stable and quick to connect, although it does suffer from some rubber banding when in heavily occupied instances; so was just wondering if it would improve anything enough to make changing it worthwhile, or is is just a suck it a see thing ?
 
XBone user here currently have Google (Public DNS) 8.8.8.8; 8.8.4.4 configured on the Xbox with a wired connection to my Plus.net Router.
Would I gain any benefit in reconfiguring to the suggested cloudfare DNS service ?

For IPv4: 1.1.1.1 and 1.0.0.1
For IPv6: 2606:4700:4700::1111 and 2606:4700:4700::1001 - [Not currently supported by Plus.net]

With what I currently have set now, Wings / Multi-Crew seem to be pretty stable and quick to connect, although it does suffer from some rubber banding when in heavily occupied instances; so was just wondering if it would improve anything enough to make changing it worthwhile, or is is just a suck it a see thing ?

I doubt you will see any difference. The DNS is just what translates URLs (think google.com or amazon.com) to their IP numbers, which is the real way computers initiate communications over the internet. Most likely, the client software connects to a static IP which then routes the client to an appropriate gateway into the servers. From there it is all direct IP communication rather than DNS translations to a site.
 
I doubt you will see any difference.

Depends; name resolution is part of the connection cycle, and given just how often frontier obsessively connect/ tear-down/ reconnect (seriously, there is a connection sonata being played every time you move between instances) slow performing DNS will slow that cycle anytime the CDN sends connections to a new host (that the player's PC hasn't got an (unexpired) cached record for).

The game has both P2P as well as amazon centric (AWS) connections going on, constantly. So yeah, actually, a fast responding DNS helps anything doing connection gymnastics; which the Elite client sure does. I'm sure you're just trying to be constructive; but it's not quite that simple. ;)

Note: DNS is simply resolution; therefore it'll impact how quickly a resource is resolved, so it can be connected to. This will have nothing to do with positional or general game performance, vis-a-vis ship movement. It may make instance changing a little snappier, as that's one of the times the client plays an opus tearing down and reconnecting to AWS.
 
Last edited:
Back
Top Bottom