Pada
Executive Member
Yes. Most of the ISP's only route the Google Searching to a local server, or very few of the Google Services.Are there really ISPs that need this still?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Yes. Most of the ISP's only route the Google Searching to a local server, or very few of the Google Services.Are there really ISPs that need this still?
Nope, that's one thing that won't workIf I use Imap for Gmail will this go through local?
On a 384 line gmail takes ages to sync via IMAP using outlook for example.
Ok I checked and this is all I got, and I can't find a way to adds mail.google.comThat's unfortunately the problem when forcing an HTTPS connection to a different serverIf you do get this issue with the certificates, PLEASE ensure that the Certificate Hierarchy tree resolves back to a Built-in Token (Root Certificate) in Firefox. You can view the Certificate and then in the Details tab it would show the Hierarchy tree.
I've updated my list in my first post by merging/adding all the DNS entries given in this thread. I've also removed all the double entries. Like www.google.com would resolve to www.l.google.com, so I've removed www.google.com.
If you have a DNS server that won't resolve www.google.com to www.l.google.com, then I would love to get that DNS server's IP address
I've used the following DNS servers to test my list: 168.210.2.2 (IS), 196.25.1.9 (Telkom), 146.232.128.10 (Stellenbosch Unversity - Internal access only) & 8.8.8.8 (Google DNS).
To check how the DNS entry is being resolved, use the command-line app: nslookup <hostname>, eg. nslookup www.google.com
In Linux you can either use nslookup or dig
TheHxckid, do you have no international cap left? Could you also tell me which lines (relevant to Gmail) you imported into your hosts file?
Please post the results of 'ping mail.google.com' and 'ping www.gmail.com' -> I'm only interested in the IP address that those hostnames resolve to.
Yes. Most of the ISP's only route the Google Searching to a local server, or very few of the Google Services.
I haven't had any trouble with Gmail on my Mweb account, using these modifications. If you guys are experiencing problems, please post your ISP package that you're using and also the DNS server IP address if you can get hold of it. Do a ping to the Gmail address that you're using, like mail.google.com or www.gmail.com and post the IP here too.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\TPex>ping mail.google.com
Pinging mail.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=158ms TTL=59
Reply from 196.23.168.147: bytes=32 time=251ms TTL=59
Reply from 196.23.168.147: bytes=32 time=322ms TTL=59
Reply from 196.23.168.147: bytes=32 time=221ms TTL=59
Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 322ms, Average = 238ms
C:\Users\TPex>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\TPex>ping mail.google.com
Pinging mail.google.com [196.23.168.147] with 32 bytes of data:
Reply from 196.23.168.147: bytes=32 time=158ms TTL=59
Reply from 196.23.168.147: bytes=32 time=251ms TTL=59
Reply from 196.23.168.147: bytes=32 time=322ms TTL=59
Reply from 196.23.168.147: bytes=32 time=221ms TTL=59
Ping statistics for 196.23.168.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 322ms, Average = 238ms
C:\Users\TPex>