cancel
Showing results for 
Search instead for 
Did you mean: 

DNS on DHCP

Tempting
Grafter
Posts: 57
Thanks: 7
Registered: ‎27-01-2016

DNS on DHCP

I think my router is the 'hub one' that people are talking about. There's a long blue light across the front when connected so this may give a clue to those more educated than myself  Smiley
Could someone please tell me where to change the DNS that are issued by DHCP on this router? I have left the LAN side IP address of my router as 192.168.1.254 and the DNS issued by DHCP is also 192.168.1.254 this fails to perform DNS lookup so I would like to change the DNS to something which actually works.
Any advice gratefully accepted.
[edit] corrected typos[/edit]
5 REPLIES
popeyeuk
Grafter
Posts: 85
Thanks: 1
Registered: ‎07-09-2010

Re: DNS on DHCP

Hi mate I have a HH5 connected to Plusnet and it's connected using the PLusnet alternate DNS servers 212.159.6.9 and 212.159.6.10..  We
seem to have been having problems all day today with very slow DNS response times
I  believe (although I haven't done it)   that if you want to change the DNS server settings in the homehub you need to go into
"advanced settings" then hit the Broadband top menu so it shows your current DNS servers down the page..  Then disconnect
using the button at the bottom of the page and you will get the option to manually add fixed DNS details..
Hope this helps Smiley))
dick:quote
Tempting
Grafter
Posts: 57
Thanks: 7
Registered: ‎27-01-2016

Re: DNS on DHCP

Many thanks for your reply popeyeuk, I can see exactly where you're talking about. I'm surprised that earlier today one of machines got the router IP as the gateway and the DNS.
I'll monitor the situation and see if it's just a one off and whether it was maybe related to the slow PN DNS response times of which you speak.
Appreciate your reply.
[Edit]Does DHCP always have to allocate the DNS which the router has obtained from PN? I thought I should be able to set the DNS allocated by DHCP on the LAN while leaving the default obtained DNS on the router alone....does that make sense?[/edit]
popeyeuk
Grafter
Posts: 85
Thanks: 1
Registered: ‎07-09-2010

Re: DNS on DHCP

Something weird is going on..  I just tried pinging Plusnets DNS servers ... and intermittently  got very slow response times..
Also tried Googles 8.8.8.8 and 8.8.4.4 with similar poor results...  I manually set my Win 10 laptop to staic Google DNS severs
and still get timeouts and very slow page loads..  Tried 2 other PC's with same results..
Seems like a network problem
Undecided Undecided
Tempting
Grafter
Posts: 57
Thanks: 7
Registered: ‎27-01-2016

Re: DNS on DHCP

I'm currently getting pings of between 10 ms - 12 ms on PN and Google's public DNS.
Something strange going on or is it still BT recovering from the other day?
popeyeuk
Grafter
Posts: 85
Thanks: 1
Registered: ‎07-09-2010

Re: DNS on DHCP

Maybe yes..  I get the following when pinging:-
Pinging 212.159.6.9 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 212.159.6.9: bytes=32 time=3957ms TTL=60
Reply from 212.159.6.9: bytes=32 time=3128ms TTL=60
Reply from 212.159.6.9: bytes=32 time=865ms TTL=60
Reply from 212.159.6.9: bytes=32 time=720ms TTL=60
Reply from 212.159.6.9: bytes=32 time=3349ms TTL=60
Reply from 212.159.6.9: bytes=32 time=545ms TTL=60
Reply from 212.159.6.9: bytes=32 time=15ms TTL=60
Reply from 212.159.6.9: bytes=32 time=19ms TTL=60
Reply from 212.159.6.9: bytes=32 time=15ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=13ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=15ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=13ms TTL=60
Reply from 212.159.6.9: bytes=32 time=14ms TTL=60
Reply from 212.159.6.9: bytes=32 time=1926ms TTL=60
Request timed out.