Yes, that sounds very odd.  I've never seen this behavior, although,
honestly, there haven't been many times where I DIDN'T want a unit to
register (only at home, to my ISP DNS, I choose to not register if I'm
using the ISP's domain suffix.)  Speaking of which, I wonder how much
oddball traffic ISPs get from the default XP/2000 system configuration
that attempts to register with the ISP's domain suffix.  I know my ISP
doesn't permit dynamic updates and unless someone manually takes this
function off, I'd guess 99% of the systems send ddns update attempts to
the ISP's dns.

Yes, I'd like to see that little reg location that you're describing

too!

Bob

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 27, 2008 10:03 PM
To: Active Directory Admin Issues
Subject: RE: Odd Dynamic DNS issues

Bob,
      No, the adapters are not running on DHCP.  None of the servers
are,
except for new ones that are just being built and later get static
addresses.  The hack that Microsoft gave us works well for stopping the
behavior.  Apparently, once a NIC dynamically registers itself, the
registration process adds a couple keys in the local registry and the
checkbox in the TCP/IP configuration no longer has any effect.  There's
no
way to turn it off except for editing the registry, which seemed odd to
me.
I can't think what else might possibly be registering them but will look
into that if we find it happening again.  MS was actually surprised that
we
hadn't had the issue earlier.  We wound up talking to a third tier
support
guy, who is the one that gave us the registry hack.  Thanks for the
input.

Regards,
Eric Harris
PC/LAN Support
NSRI (USA), Inc.
(206)464-5194





 

             "Fuller, Bob"

             <[EMAIL PROTECTED]

             alihan.com>
To 
                                       "Active Directory Admin Issues"

             01/26/2008 01:26
<[email protected] 
             AM                        >

 
cc 
 

             Please respond to
Subject 
             "Active Directory         RE: Odd Dynamic DNS issues

               Admin Issues"

             <[EMAIL PROTECTED]

             nbelt-software.co

                    m>

 

 





Is something perhaps registering the 2nd address on behalf of the
servers? If you're setting the individual servers to not register, it
would seem reasonable to think that they're not registering.

You might delete a record on the DNS server that's got the bad record,
then set up a packet monitor to capture your dns traffic, just to see if
it's a DDNS Update or Registration coming from somewhere other than the
DNS server or the referenced server themselves.

Are your DDNS set for unsecured registration?  Those adapters on the 2nd
net, aren't running  via DHCP are they?

Bob

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 12:55 PM
To: Active Directory Admin Issues
Cc: [EMAIL PROTECTED]
Subject: Odd Dynamic DNS issues


To All,
      If there is a better forum for this question, my apologies and
thanks
if you can redirect me.

      We have several Windows 2003 domains in our environment and
utilize
dynamic DNS.  We have multiple internal servers which have 2 NICs in
them.
One NIC is on a general access subnet.  The other NIC is on a private
subnet used for backups with no public access to it.  Over the last two
weeks we have had issues with the backup IP addresses turning up in DNS
even when the check box in the TCP\IP settings for registering the IP
address in DNS is NOT checked.  This causes DNS resolution problems, of
course.
      The problem seems to be isolated to one Windows domain but not all
servers in the domain have the problem.  The DNS server is in a
different
domain.  On the servers that have the problem, the DDNS checkbox seems
to
be irrelevant.  The problem does not change whether we check the box or
not, so enabling registration and then disabling it does not make a
difference.  So far as we know, no patching has been done that would
affect
this.
      We have found a registry hack that does seem to fix the problem
but
no one (we even called Microsoft) has been able to suggest a possible
cause
for this.  We would like to know what is causing the problem in the
interest of prevention.  Ideas?  Suggestions?

Regards,
Eric Harris
PC/LAN Support
NSRI (USA), Inc.
(206)464-5194




~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK
Test! ~
    ~  <http://www.sunbelt-software.com/product.cfm?id=400>  ~

~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK
Test! ~
    ~  <http://www.sunbelt-software.com/product.cfm?id=400>  ~




~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK
Test! ~
    ~  <http://www.sunbelt-software.com/product.cfm?id=400>  ~

~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~
    ~  <http://www.sunbelt-software.com/product.cfm?id=400>  ~

Reply via email to