Event ID 4321: 'The name DOMAIN :1d" could not be registered
Hello,
I'm trying to figure out why a SQL Server on our domain is logging this error every 30mins or so.
The name "DOMAINNAME :1d" could not be registered on the Interface with IP address 10.92.8.85. The machine with the IP address 10.138.253.16 did not allow the name to be claimed by this machine.
One of our AD DCs is 10.138.253.16. It is also the DHCP server provisioning this SQL server with its IP address.
An ipconfig from the SQL server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : flsqlecc05
Primary Dns Suffix . . . . . . . : domainname.co.uk
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.co.uk
search.domain1
search.domain2
Ethernet adapter Team nic:
Connection-specific DNS Suffix . : domainname.co.uk
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-1E-0B-CE-4A-18
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.92.8.85
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.92.8.1
DHCP Server . . . . . . . . . . . : 10.138.253.16
DNS Servers . . . . . . . . . . . : 10.90.8.201
10.90.8.24
Lease Obtained. . . . . . . . . . : 06 October 2009 13:38:48
Lease Expires . . . . . . . . . . : 14 October 2009 13:38:48
We do not use WINS and this server is not cloned so no duplicate SIDs.
Can anyone offer an explanation as to what is casuing this?
Thanks
Steve
I'm trying to figure out why a SQL Server on our domain is logging this error every 30mins or so.
The name "DOMAINNAME :1d" could not be registered on the Interface with IP address 10.92.8.85. The machine with the IP address 10.138.253.16 did not allow the name to be claimed by this machine.
One of our AD DCs is 10.138.253.16. It is also the DHCP server provisioning this SQL server with its IP address.
An ipconfig from the SQL server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : flsqlecc05
Primary Dns Suffix . . . . . . . : domainname.co.uk
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domainname.co.uk
search.domain1
search.domain2
Ethernet adapter Team nic:
Connection-specific DNS Suffix . : domainname.co.uk
Description . . . . . . . . . . . : HP Network Team #1
Physical Address. . . . . . . . . : 00-1E-0B-CE-4A-18
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.92.8.85
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.92.8.1
DHCP Server . . . . . . . . . . . : 10.138.253.16
DNS Servers . . . . . . . . . . . : 10.90.8.201
10.90.8.24
Lease Obtained. . . . . . . . . . : 06 October 2009 13:38:48
Lease Expires . . . . . . . . . . : 14 October 2009 13:38:48
We do not use WINS and this server is not cloned so no duplicate SIDs.
Can anyone offer an explanation as to what is casuing this?
Thanks
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
To fix this, we will need your Network topology.
We will also need the IPs of the DCs as well as who is supplying DHCP and DNS.
We will also need the IPs of the DCs as well as who is supplying DHCP and DNS.
The DHCP may not be the best setup, but if you use reservations it can work just fine. I wouldn't do it either. However it is not necessary to have a DNS server or a DHCP server in the same subnet. For DNS it doesn't matter at all, and for DHCP servers you can use relay agents or special configuraton on routers and switches. DNS also has nothing to do with the error they are getting.
ASKER
nbtstat reported no conflicts.
I will keep an eye on it for now, but it seems fairly benign.
I will keep an eye on it for now, but it seems fairly benign.
ASKER
Thanks for the suggestions here.
The server in question has only 1 NIC, sorry ChiefIT.
Wonko - DHCP is used for DR reasons. A reserved IP address is present at 2 datacentres for this SQL server. This speeds up DNS auto updates and simplifies the failover / failback process. Therefore as long as we haven't 'failed over' the IP always remains the same.
Regards
Steve
The server in question has only 1 NIC, sorry ChiefIT.
Wonko - DHCP is used for DR reasons. A reserved IP address is present at 2 datacentres for this SQL server. This speeds up DNS auto updates and simplifies the failover / failback process. Therefore as long as we haven't 'failed over' the IP always remains the same.
Regards
Steve
I see a lot of potential discrepancies on this LAN and would like to help you rid yourself of these:
Let's go over them:
IP Address. . . . . . . . . . . . : 10.92.8.85<<<<<<<<<<<<Your
Subnet Mask . . . . . . . . . . . : 255.255.255.0<<<<<<<<<Your
Default Gateway . . . . . . . . . : 10.92.8.1<<<<<<<<<<<Your gateway is on the same subnet
DHCP Server . . . . . . . . . . . : 10.138.253.16<<<<<<<<Your DHCP Server is not on the same subent
DNS Servers . . . . . . . . . . . : 10.90.8.201<<<<<<<<<Your DNS server is not on the same subnet
10.90.8.24<<<<<<<<<<<<<<Yo
DHCP is enabled:
This means you are getting DHCP from the DHCP server, (not a fixed IP). Thats difficult for a SQL server.
You are trying to renew your IP address within DHCP and it will not allow you to reclaim it. You have what appears to be two adapters that are getting DHCP, Your DNS servers are not within your network and may not be able to point back to it with DNS resolution. Your DHCP server is not on the same broadcast domain, so it may have problems with DHCP. Your DHCP server is passing down the wrong DNS addresses to its clients. Your SQL server is not on a Fixed IP, and periodically it may be hard to reach.
See how these things may cause problems.