Doesn't really make any difference - my original comments still apply. I
wouldn't bother trying to have the gateway do any DNS 'proxying' - what's
the purpose? It doesn't do anything for security, and it isn't working. :-)
Doug wrote:
> Ok, My error on one point that may affect the analysis. The device is
> actually a "3Com Office Connect Cable/DSL Secure Gateway" Therefore
> I do believe it is the job of this device to proxy the DNS.
>
> Please review the original issue below that I have been having.
>
> Thanks,
>
> Doug
>
>
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed)> wrote in
> message news:(E-Mail Removed)...
>> Doug wrote:
>>> That has worked in the heat of the moment to get connected. But I
>>> really shouldn't have to re-configure each workstation to point to
>>> our ISP. That's what the job of the router is, isn't it ?
>>
>> No, the basic job of the router is to route traffic between networks
>> - not to proxy DNS.
>>
>> As we grow,
>>> I don't want to have to adjust 100 workstations if we change ISP's.
>>
>> That's what DHCP is for - your router should be able to do it. :-)
>>>
>>> Any other thoughts ?
>>>
>>> Thanks,
>>>
>>> Doug
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed)> wrote in
>>> message news:(E-Mail Removed)...
>>>> What if you change the DNS server IPs to those of your ISP instead?
>>>>
>>>> Doug wrote:
>>>>> I say it's the router, our vendor says it my set-up. I have a 3Com
>>>>> router that contains a firewall and VPN capability. It is the link
>>>>> between my DSL modem and the rest of my network. For over eight
>>>>> months, things have been working fine with my network setup with
>>>>> static IP's (relatively small network).
>>>>>
>>>>> The router is configured with the DSL login info, DNS's etc. The
>>>>> workstations are configured to use the router's local IP (all
>>>>> local is in the 192.168.xxx.xxx range) for the gateway and the
>>>>> primary DNS. This has been working fine until recently we get
>>>>> intermittent loss of DSL service. By intermittent, some
>>>>> workstations get email, some don't; some people can browse, some
>>>>> can't; some get email but cannot browse, etc.
>>>>>
>>>>> By unplugging the power to the router for a few minutes and
>>>>> plugging it back in and rebooting, everything comes back to
>>>>> normal. At least for a while, it may last a day, it may last two
>>>>> hours.
>>>>>
>>>>> I say there is a problem with the router. My vendor who sold me
>>>>> the router says the only way to fix it is to start using DHCP. If
>>>>> this was the case, why would it have worked fine for over 8
>>>>> months.
>>>>>
>>>>> Any suggestions ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Doug
|
Similar Threads
