Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The preferred DNS server on the new network refuses requests #215

Closed
amcewen opened this issue Nov 5, 2015 · 12 comments

Comments

@amcewen
Copy link
Member

commented Nov 5, 2015

The new faster Internet connection gives out 79.98.167.69 as the primary DNS server, but that server refuses requests.

I've been getting regular DNS failures in general browsing - refreshing the page a few times will eventually pick up the DNS from the secondary server, but it's not ideal.

Trying to set up the Air Quality Egg that we've been given this evening, that only uses the primary DNS server, and so can't connect out to the Internet at all. I've tried setting it to use IP addresses rather than hostnames, but it doesn't seem to support that :-(

@DefProc

This comment has been minimized.

Copy link

commented Nov 5, 2015

Can we change the DNS settings on the router? Would it be better to
switch it to OpenDNS or somewhere else if we're having problems?

On 05/11/15 19:36, Adrian McEwen wrote:

The new faster Internet connection gives out 79.98.167.69 as the
primary DNS server, but that server refuses requests.

I've been getting regular DNS failures in general browsing -
refreshing the page a few times will eventually pick up the DNS from
the secondary server, but it's not ideal.

Trying to set up the Air Quality Egg that we've been given this
evening, that only uses the primary DNS server, and so can't connect
out to the Internet at all. I've tried setting it to use IP addresses
rather than hostnames, but it doesn't seem to support that :-(


Reply to this email directly or view it on GitHub
#215.

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Nov 5, 2015

I couldn't find a setting for that, I'll ping the support address to see what they say.

On 5 Nov 2015, at 21:28, Patrick Fenner notifications@github.com wrote:

Can we change the DNS settings on the router? Would it be better to
switch it to OpenDNS or somewhere else if we're having problems?

On 05/11/15 19:36, Adrian McEwen wrote:

The new faster Internet connection gives out 79.98.167.69 as the
primary DNS server, but that server refuses requests.

I've been getting regular DNS failures in general browsing -
refreshing the page a few times will eventually pick up the DNS from
the secondary server, but it's not ideal.

Trying to set up the Air Quality Egg that we've been given this
evening, that only uses the primary DNS server, and so can't connect
out to the Internet at all. I've tried setting it to use IP addresses
rather than hostnames, but it doesn't seem to support that :-(


Reply to this email directly or view it on GitHub
#215.


Reply to this email directly or view it on GitHub #215 (comment).

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Nov 5, 2015

Speedy response from Efuse, unfortunately it looks like this is set (or at least specified) downstream (by Metronet?) so they can't do anything in the short term. Annoyingly of course if we'd left the TP-Link in place we wouldn't have this problem! I can try checking if the Airport will let me set alternative DNS settings or you could ask a mac user tomorrow to see if they can (I think at the moment they won't need an admin password).

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Nov 5, 2015

"It might be a temporary issue on this primary DNS server so we are raising a quick ticket with the host. If by tomorrow pm this is not resolved we will permanently switch 8.8.8.8 to be the primary DNS."

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Nov 5, 2015

Cool. I'd also had a poke around to see if we could change it and couldn't spot anywhere that we could.

@johnmckerrell

This comment has been minimized.

Copy link
Member

commented Nov 6, 2015

"Found another DNS specified by the core ISP so we have just replaced the primary DNS with 77.75.184.5. Please feel free to test again. The change is permanent."

Any better?

Sent from my mobile phone hence brevity and errors

On 5 Nov 2015, at 23:02, Adrian McEwen notifications@github.com wrote:

Cool. I'd also had a poke around to see if we could change it and couldn't spot anywhere that we could.


Reply to this email directly or view it on GitHub.

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Nov 6, 2015

Seems to be working fine today, and the Air Quality Egg has been able to get online successfully too. Thanks for sorting it out @johnmckerrell!

@amcewen amcewen closed this Nov 6, 2015

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Jan 20, 2016

Hmm, "The change is permanent" until it isn't. The past couple of days I've been getting DNS failures again. Checking with wireshark now it seems I'm being given 79.98.167.69 again as the primary DNS, and still getting refusals from it.

It seems that we can set DNS servers in the admin for the router, but that requires a reboot of it. I'll give that a try when things are quieter in the office

@amcewen amcewen reopened this Jan 20, 2016

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Jan 20, 2016

I suspect this will be causing the problem with the heating in issue #251, given that the Arduino DNS client just takes the first DNS server it's given in the DHCP response...

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Jan 20, 2016

The manual ones were set to (although the manual DNS setup wasn't enabled):

  • 168.126.63.1
  • 168.126.63.2

I've updated them to:

  • 77.75.184.5
  • 8.8.8.8

And that seems to have improved matters for my laptop. Sadly it didn't seem to fix issue #251 :-/

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Jan 21, 2016

Spoke too soon - it hasn't fixed issues for my laptop, but I'm still being given 79.98.167.69 as the primary DNS.

So I don't know what the DNS server setting in the router actually does, but it doesn't appear to fix things :-/

I've emailed our Internet provider's support to hopefully get it resolved.

@amcewen

This comment has been minimized.

Copy link
Member Author

commented Jan 22, 2016

Has been fixed again now.

@amcewen amcewen closed this Jan 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.