Dynamic DNS Not Updating for Windows 2000

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have Windows 2000 servers that are not able to update using Dynamic DNS
when I run ipconfig /registerdns. After 15 min, nothing shows up in event
viewer. I have checked the DHCP Client service. It's running. I've also
checked the "Register ... with DNS" box. I checked the registry as well for
that interface. DNS suffixes and Computer ID info is set correctly. All the
typical stuff seems to be ok. I even ran netmon to see if I could see if
server was doing anything, but it doesn't seem like it was even making an
attempt (no frames captured). I also verified again using windump.

Am I missing something else that is preventing it from actually working?
Works fine for Windows 2003 servers.

thanks
 
In
bui said:
I have Windows 2000 servers that are not able to update using Dynamic
DNS when I run ipconfig /registerdns. After 15 min, nothing shows up
in event viewer. I have checked the DHCP Client service. It's
running. I've also checked the "Register ... with DNS" box. I
checked the registry as well for that interface. DNS suffixes and
Computer ID info is set correctly. All the typical stuff seems to be
ok. I even ran netmon to see if I could see if server was doing
anything, but it doesn't seem like it was even making an attempt (no
frames captured). I also verified again using windump.

Am I missing something else that is preventing it from actually
working? Works fine for Windows 2003 servers.

thanks
Click to expand...

Can you post an ipconfig /all please to give us a better idea of your
configuration?


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================
 
Ace -
Here's the ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server16
Primary DNS Suffix . . . . . . . : msad.bdc.lex.remy.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : msad.bdc.lex.remy.com
bdc.lex.remy.com
us.remy.com
remy.com
lex.remy.com

Ethernet adapter User Network:

Connection-specific DNS Suffix . : msad.bdc.lex.remy.com
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-8B-45-F2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 12.169.40.178
Subnet Mask . . . . . . . . . . . : 255.255.255.224
IP Address. . . . . . . . . . . . : 12.169.40.177
Subnet Mask . . . . . . . . . . . : 255.255.255.224
IP Address. . . . . . . . . . . . : 12.169.40.176
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 12.169.40.161
DNS Servers . . . . . . . . . . . : 12.169.40.41
12.169.40.42

Ethernet adapter Backup Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC #2
Physical Address. . . . . . . . . : 00-02-A5-8B-45-F1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.40.176
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
 
In
bui said:
Ace -
Here's the ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : server16
Primary DNS Suffix . . . . . . . : msad.bdc.lex.remy.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : msad.bdc.lex.remy.com
bdc.lex.remy.com
us.remy.com
remy.com
lex.remy.com

Ethernet adapter User Network:

Connection-specific DNS Suffix . : msad.bdc.lex.remy.com
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-02-A5-8B-45-F2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 12.169.40.178
Subnet Mask . . . . . . . . . . . : 255.255.255.224
IP Address. . . . . . . . . . . . : 12.169.40.177
Subnet Mask . . . . . . . . . . . : 255.255.255.224
IP Address. . . . . . . . . . . . : 12.169.40.176
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 12.169.40.161
DNS Servers . . . . . . . . . . . : 12.169.40.41
12.169.40.42

Ethernet adapter Backup Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet
NIC #2 Physical Address. . . . . . . . . : 00-02-A5-8B-45-F1
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.40.176
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Click to expand...


Thanks for posting the ipconfig.

I can see partially why it may not be registering because of all the IPs on
one NIC, and it's a multihomed machine., but will need a little more info.

Is this a domain controller? If so, multihomed DCs are very problematic if
not configured properly, especially when there are multiple IPs on top of
that. Multi NICs and IPs are best left for a member server to insure DC
functionality.

In Network Connections property, Adv menu, Adv Settings, which NIC is on the
top of the binding order?

What is the zone name in DNS called that you want it to update into? Is it
"msad.bdc.lex.remy.com"? The Primary DNS Suffix is what teh system looks for
when registering, then it chooses the first DNS in the list.

Are these two DNS addresses listed your internal DNS?
DNS Servers . . . . . . . . . . . : 12.169.40.41
12.169.40.42
Click to expand...

For "Register this connection" checkbox, which zone name do you have it set
to register into?

Ace
 
Server is not a domain controller.
Zone name is msad.bdc.lex.remy.com.
Primary DNS suffix for this system is msad.bdc.lex.remy.com
Not sure about the binding order. This is a dual port card and the main
user interface is on port 1.
"Register this connection" check box is set to msad.bdc.lex.remy.com

Let me know if you need additional info.
 
In
bui said:
Server is not a domain controller.
Zone name is msad.bdc.lex.remy.com.
Primary DNS suffix for this system is msad.bdc.lex.remy.com
Not sure about the binding order. This is a dual port card and the
main user interface is on port 1.
"Register this connection" check box is set to msad.bdc.lex.remy.com

Let me know if you need additional info.
Click to expand...

Are these two DNS addresses listed your internal DNS?
DNS Servers . . . . . . . . . . . : 12.169.40.41
12.169.40.42
Click to expand...

Does the zone allow updates?

Ace
 
Yes, zone allows updates (secure only since we are using AD-integrated).
Windows 2003 servers are able to update.
 
In
bui said:
Yes, zone allows updates (secure only since we are using
AD-integrated). Windows 2003 servers are able to update.
Click to expand...

Third time asking, so I am assuming these are your internal servers:

The only other thing I can think of is, based on your netmon capture saying
you don't even see it attempting a registration, that this machine has a reg
entry stopping it or, a service is disabled, but I don't think it's because
this machine is not joined to the domain (Secure updates).

I made this list in the past, but it seems you got most if not all covered:

DNS Dynamic Registration:
1) External DNS servers are configured under TCP/IP properties. Only use
internal DNS servers when part of an Active Directory domain. AD Domain
machines must never be pointed at an external (ISP) DNS server or even use
an ISP DNS server as an "Alternate DNS server".
2) AD/DNS zone not configured to allow dynamic updates.
3) 'Register this connection's address" in DNS is not enabled under TCP/IP
properties.
4) Not authenticated to the domain (due to DNS misconfiguration or DNS
server problem)
5) Missing or incorrect "Primary DNS suffix" or "Connection-specific DNS
suffix" of the domain to which the machine belongs. With a
missing/incorrect DNS suffix a machine cannot find the correct zone to
register in.
6) A Group Policy is forcing secure updates and the machine isn't a member
of the domain..
7) DHCP client service not running. This is a requirement for DNS
registration and DNS resolution even if the client is not actually using
DHCP. See the below articles.
8) Reg entry stopping it:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804
9). It's got some sort of malware or virus altering network services
preventing it from registering.

Maybe it has to do with all the IPs, but I really seriously doubt that.


Ace
 
Back
Top