| 1 |
On 11/07/2016 22:29, Grant Edwards wrote: |
| 2 |
> On 2016-07-11, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> why don't you go with the dns server addresses supplied by each |
| 5 |
>> network's dhcp? Presumably the admin put them their because they |
| 6 |
>> work on that network. |
| 7 |
> |
| 8 |
> One might think that, but I find it often not to be the case. I can |
| 9 |
> recall many networks where the DNS servers returned by the DHCP server |
| 10 |
> didn't work well at all, and things got a _lot_ better when I manually |
| 11 |
> configured a couple working DNS servers (e.g. the Google ones at |
| 12 |
> 8.8.8.8 and 8.8.4.4). Around here, Comcast's DNS servers are famously |
| 13 |
> bad. |
| 14 |
> |
| 15 |
|
| 16 |
Then shoot the idiot running that wireless network. If he's one of my |
| 17 |
juniors, tell me so I can fire him (as he's just proved he can't do the |
| 18 |
job he's paid to do) |
Archives