Android devices fail to connect when I set a custom dns server in the same range.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Android devices fail to connect when I set a custom dns server in the same range.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
So,
1.
I reset my router to factory
Router default ip is 192.168.0.1
Set DHCP main DNS server to 192.168.0.X example 192.168.0.10
Result:
Any android device cannot stablish a connection to the router, it automatically disconnects and enters a connection loop
2.
If I set the DNS server to 192.168.1.X while the router IP is 192.168.0.1 it works.
So basically if I set a DNS in the same IP range as the router, it fails, and I need the DNS server on the same range as the router....
what can I do? and I cannot manually set every PC dns manually, I need this in the router.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@terziyski thanks but I already tried it, is not that. I have my dns setup in the DHCP server.
The dns work fine on PC or laptops, the problem is when Android devices try to connect to the WiFi, it reconnects indefinitely not even 1 second and it disconnect/reconnect.
And basically any android device, not just 1 or 2... I cannot test on iOS.
- Copy Link
- Report Inappropriate Content
Maybe the problem is with your DNS setup or the way Android OS devices communicate with this DNS.
Many users are using a Pi-hole in their environment and configure the DNS in the router's DHCP settings without any issue.
What kind of SW you're using for your DNS ?
Have you considered upgrading your router's FW to the latest release ?
- Copy Link
- Report Inappropriate Content
@terziyski I don't remember, I didn't setup that dns... but here is the fun part. is not the dns server, I tested all this without connecting anyting but my wifi to the android...
I also configured a different router (not archer c50) with the exact dns and subnet, and works perfectly.... I think it's a bug in the archer firmware that makes androids fail to connect when they see this setup.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@terziyski done and the issue persists
- Copy Link
- Report Inappropriate Content
What is the default DNS server obtained automatically on the router? What is the reason that you need to modify it manually to 192.168.0.1?
- Copy Link
- Report Inappropriate Content
@Kevin_Z The default DNS when is factory is 192.168.0.1 if I recall correctly.... and I need to manually modify the DNS server to in the DHCP server in the router to 192.168.0.104 as there is a local DNS server in that address that is needed for local computers in my network... the router default ip address is 192.168.0.1 I dont change that.
Maybe try it on any tplink router and then try to connect via wifi with your android phone (I have android 11)
- Copy Link
- Report Inappropriate Content
Can we have the specific brand and model of those Android 11 devices that having an issue connecting to the network once you manually change the DNS server to 192.168.0.104?
- Copy Link
- Report Inappropriate Content
Thats interesting, I never had the idea to test older android phones, I tried some old samsung tablets, zte phones and it works fine.
I tried on some Xiaomi phones with android 11 Poco X3, Redmi 7 Redmi 8, and they all fail with this setup, I also found that If i setup a second DNS like 8.8.8.8 keeping 192.168.0.104 as main dns it works fine with the xiaomi phones.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2384
Replies: 12
Voters 0
No one has voted for it yet.