Posted: Mon Nov 29, 2021 19:36 Post subject: Not able to access domain pointing to my IP address
Hello,
Not sure I have posted in the right part of the forum, but here it is:
I have an issue where I'm not able to resolve domains that are pointing to my IP address when I'm inside the network (This site can’t be reached), regardless the client used (mobile, pc) or the internet browser used.
You have the network topology attached.
When pinging 1.mysupersecretdomain.tld it goes to 123.45.6.7, so it is indeed pointing where it is supposed to.
Pinging 1.mysupersecretdomain.tld [123.45.6.7] with 32 bytes of data:
Reply from 123.45.6.7: bytes=32 time<1ms TTL=64
Reply from 123.45.6.7: bytes=32 time=2ms TTL=64
Reply from 123.45.6.7: bytes=32 time<1ms TTL=64
Reply from 123.45.6.7: bytes=32 time<1ms TTL=64
Ping statistics for 123.45.6.7:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms
The funny thing (which is driving me mad) is that, when using the LTE connection with my mobile phone, the web page is loading just fine, SSL is in place, as it should be. Simply put, when trying to access 1.mysupersecretdomain.tld outside my network, everything works as expected.
Any ideas before I decide to smash the router with a hammer? It's obviously something I'm doing wrong with my router config, altough I don't have anything fancy in place. Only 2 isolated VAPs with different DHCP servers and a Wireguard server. _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
Thank you for your reply. I have tried that, but it doesn't work. I can't access 1.mysupersecretdomain.tld. Additionally, the DHCP fails. In order to get a valid IP address, I will have to set it manually on the client. Connecting to a Wi-Fi doesn't works as o result of DHCP not working. _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Mon Nov 29, 2021 21:08 Post subject:
Then there is another problem elsewhere with your configuration. I can only guess you are using the static IP inputs on the main page, querying in strict order, and not using a no-resolv directive with server= entries in your additional dnsmasq config, among other things. Best way is to provide visuals of your applicable configurations and more information so we can have a better chance at successfully troubleshooting this. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
DHCP-Authoritative is disabled
Recursive DNS Resolving (Unbound) is disabled
Forced DNS Redirection is disabled
Other than that, please check the attachment. If there is anything else that you feel like it is relevant, please let me know.
And yes, the DNS was set from main page, not from additional dnsmasq options. I have tried without DNS servers (just using the ISP-provided DNS servers) and it's still not working... _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
