From: Andrew M. Saucci, Jr. on
While I have occasionally had problems with hardware updaters being
blocked, they are far less severe and far less frequent than problems I've
had with software updaters, which are junk-- I don't care what DynDns says
about them. A firmware update will generally fix problems with hardware
updaters. Junky software updaters just never belong on an SBS.

I also object to the term "abuse" in this context. (I know-- it's
their term, but I object nonetheless.) The word has too many moral overtones
when all we're discussing here is a piece of computer equipment somewhere.
They make it sound as though they're some sort of angels for deigning to
provide such a service to us lowly network consultants-- nothing like
lording it over inferiors.

"Russ SBITS.Biz [SBS-MVP]" <russ(a)REMOVETHIS.sbits.biz> wrote in message
news:E5D15E5E-370A-4B7C-9488-EF5B51D08061(a)microsoft.com...
> unfortunately with Dyndns.org
> most routers update too quickly now for them
> and you get a "you are updating too often"
> and if you do not use their software, they suspend your account for abuse
> :(
>
> Dlink has their own free service also with it built into their routers.
>
> Russ
>
> --
> Russell Grover - SBITS.Biz [SBS-MVP]
> MCP, MCPS, MCNPS, SBSC
> Small Business Server/Computer Support - www.SBITS.Biz
> Question or Second Opinion - www.PersonalITConsultant.com
> BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com
> http://www.twitter.com/SBITSdotBiz
>
> "Andrew M. Saucci, Jr." <spam-only(a)2000computer.local> wrote in message
> news:eN54kW51KHA.4560(a)TK2MSFTNGP02.phx.gbl...
>> Better still, don't ever use software updaters-- they are
>> terrible. I always use an updater built into a hardware router or
>> firewall.
>>
>> "Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message
>> news:D960379B-CDEA-4163-BA1B-23D235149D6E(a)microsoft.com...
>>> It sounds like you already know the answer. Your DynDNS updater is
>>> making changes for you. You'll have to review that documentation and
>>> may have to contact them to resolve the issue.
>>>
>>> With that said, a virtualization host OS should *just* be a host OS.
>>> The DynDNS updater should not be installed on the host OS at all.
>>> Install it on one of the child OS's if you must, but not the host.
>>>
>>> -Cliff
>>>
>>>
>>> "James" <jj(a)nomail.nomail> wrote in message
>>> news:uHfS7811KHA.4724(a)TK2MSFTNGP02.phx.gbl...
>>>> 216.146.35.35
>>>> 216.146.35.36
>>>>
>>>> Hi,
>>>>
>>>> I have Server 2008 (not R2) with Hyper-V role installed. There are two
>>>> NICs - for internal and external network (there is also virtual SBS
>>>> 2003 as main server). Everything worked fine 8 months and few days ago
>>>> I had an error. Trying to resolve this issue I removed both virtual
>>>> NICs, added it again and now DNS on NIC is very strange.
>>>>
>>>> First NIC has DG to ADSL router and DNS1 to ADSL router and DNS2 to
>>>> ISP.
>>>> After 1-2 mins both DNS IP addresses are automatically changed to
>>>> 216.146.35.35 and
>>>> 216.146.35.36 ?! Why happened that? If I change it, it will
>>>> automatically modify again.
>>>> I found that IP address belong to dyndns organization (if is it true)
>>>> and DYNDNS client updater is installed on that machine.
>>>>
>>>> Second NIC has only one DNS - main SBS server, and similar afer 1-2 it
>>>> is changed to 216.146.35.35 and 216.146.35.36.
>>>>
>>>>
>>>> Regarding this I have behavior like slow login to computer, which is
>>>> related to wrong DNS on internal NIC.
>>>>
>>>> What happened, how can I resolve it.
>>>>
>>>> Thank you in advance!
>>>>
>>>> Regards
>>>>
>>>>
>>>>
>>
>>


From: Bill Sanderson on
Great - sorry I was absent for a bit.

The current version at dyndns.org does indeed allow you to uncheck this
option.



"James" <jj(a)nomail.nomail> wrote in message
news:#Iphj$G2KHA.3844(a)TK2MSFTNGP05.phx.gbl...
> "Bill Sanderson" <bill_sanderson(a)msn.com.plugh.org> wrote in message
> news:B7FDA9B4-9208-4A8B-BB2E-2F30AF5DB394(a)microsoft.com...
>> Yuck! If there's no way to turn this off, I'm going to guard a local
>> copy of the installer for the older version like gold...
>>
>
> I found 3.0 version and it really works as before!
>