Link to home
Create AccountLog in
Avatar of Josh Fialkoff
Josh FialkoffFlag for United States of America

asked on

Site cannot be reached ONLY when connected to modem

When I try to access a specific site, I get this error message:

This site can’t be reached

__.org’s server DNS address could not be found.
Search Google for ___ org
ERR_NAME_NOT_RESOLVED

User generated image
I have tried flushing my DNS cache using this methodology: https://help.dreamhost.com/hc/en-us/articles/214981288-Flushing-your-DNS-cache-in-Mac-OS-X-and-Linux.
I have power cycled my modem and router
I have connected to my modem via Ethernet cable, bypassing the router

What do you recommend?
Avatar of John
John
Flag of Canada image

Site cannot be reached ONLY when connected to modem

So you connect via router and it works; you connect direct to modem and it does not. Correct?

Call the ISP and ask them to flush the modem and then connect. Do the latter while they are on the phone with you.
Avatar of Josh Fialkoff

ASKER

Hi John,
I did that and it did not help.
I also did a hard reset of my modem (using a pen tip on the reset button).
What else do you recommend?
Thanks,
Josh
Still connecting to the modem, try the following TCP/IP Reset
      
Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer

See if that helps.
Thanks! Will that command work on a Mac?
No. You need to find a MAC reset command. I think you can reinstall the Network card to do this.
I have renewed the DHCP lease.
Avatar of Shaun Vermaak
Visit http://downforeveryoneorjustme.com/ and type the site and check.
Please post results
It's just me... We've already established that.
ASKER CERTIFIED SOLUTION
Avatar of Ramin
Ramin

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
That did it @ramin! Thanks! What does that mean is the problem?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Great! Thank you so much!
I would not leave it at that. Change it back to DHCP and look at what entry it gets.
Avatar of Ramin
Ramin

Actually, it is the DNS server of Google, it means that Google provides the DNS and maintenance of this service, which means it is "more reliable" than some another DNS servers due to the fact that is maintained by one of the biggest IT companies of the world.
Thanks. I tried to do this, but I'm not sure what you mean, exactly. Here's a video: https://monosnap.com/file/UbEUWWD4thNSTMftVQwlLcOGL1g4q8.
Please let me know what you recommend.
My point is that if this is an environment where there is an internal DNS server (or the router acting as a DNS forwarder), it should point to the internal DNS server which in turn forwards requests to 208.67.222.222, 208.67.220.220, 8.8.8.8, 4.4.4.4 etc., it is not solving the root cause by specifying a static, external DNS server on the client side
@fialkoff:  Thanks and I was happy to help.