DNS problem

[budgetpcguy]

so i have a linksys WiFi router connected through Ethernet to a windstream modem and every WiFi connection works EXCEPT for the linksys access point ive tried alot of things and nothing worked. is it possible that my router just basically died on me?

[Granular]

What does this have to do with DNS?

Also, what are the wifi connections that are working? Dos the modem have an access point built in?

And what are the symptoms of wifi connections 'not working'? Like do the client devices see the network of the linksys router? Do they establish connections? Do they get addresses?

[budgetpcguy]

3 hours ago, Granular said:

What does this have to do with DNS?

Also, what are the wifi connections that are working? Dos the modem have an access point built in?

And what are the symptoms of wifi connections 'not working'? Like do the client devices see the network of the linksys router? Do they establish connections? Do they get addresses?

1. when i ran the windows trouble shooter it said the dns is not responding 

2. my phones mobile hotspot and my modems built in 500kb/s access point

3. they see the access point and connect to it but i get a dns error in chrome(and any other program)

Edited October 7, 2018 by budgetpcguy
misspell

[Granular]

So, if you connect to the access point and ping some public ip like 1.1.1.1, you get a response?

If yes, then go to the adminstration page for the access point and configure that to be the DNS server clients are instructed to use. Or configure your client devices to use it as their DNS server manually when using the connection.

[budgetpcguy]

3 hours ago, Granular said:

So, if you connect to the access point and ping some public ip like 1.1.1.1, you get a response?

If yes, then go to the adminstration page for the access point and configure that to be the DNS server clients are instructed to use. Or configure your client devices to use it as their DNS server manually when using the connection.

I=i cannot thank you enough i changed my static dns to 1.1.1.1 and the second one to 1.0.0.1 and it fixed it

 

[budgetpcguy]

it stoped working again