Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="azhrei_fje" data-source="post: 4870265" data-attributes="member: 12966">It is always best to use the DNS addresses that your ISP provides.  The reason is that some DNS servers (most?) will refuse DNS requests from clients they don't recognize as a way of reducing their load.  So if you're a client on one ISP's network and try to use the DNS servers of another ISP (or, potentially, even other DNS servers of the same ISP) your requests for DNS could be ignored.If I were the network admin at an ISP, that's what I'd do. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />If the problem he's having is DNS, then this will also produce a DNS error.  The only way for him to know if it's a DNS problem (other than carefully reading the error message page the browser shows him!) would be to visit a site that allows you to type in a name and get their IP address, such as going to <a href="http://netcraft.com/" target="_blank">http://netcraft.com/</a> and typing the domain name into the search box in the upper left.  You'll eventually get a single page with their IP address.  You can try putting that into your browser's Address bar and see what you get...  (May not work if they're using name-based virtual hosting, which many sites use.)Doesn't help much since many firewalls in front of web servers will block the ICMP "echo request" packet (commonly referred to as the ping packet).I would suggest that the OP start by resetting his router back to Factory Defaults.  That will clear any domain-based filtering done by the router.  (I use such filters on my router to block ad-related sites like doubleclick.net and similar.)</blockquote>

Verification