Incorrect Primary DNS Suffix

[Paul Pearce]

Hello

We just recently changed our domain name from abc.com to
def.com for our internal network.

We now have a number of PCs that are registering in DHCP
as MachineName.abc.com instead of with the new DNS suffix.

When I IPCONFIG one of the PCs, it shows the Primary DNS
suffix as abc.com and the DNS Suffix Search list as
abc.com first, then def.com next.

I've looked in all the expected places for supplying this
suffix value, but everything is set as should be.

The affected PCs are all running W2K, connecting thru a
Server 2003 Domain Controller, are identical PCs (we have
a real mix in this shop!) and may have been installed
using RIS. I'm not sure on this last part as I'm new here.

I did a quick search of the registry on one PC and found
one setting for abc.com in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ADs\Providers\LDAP
\CN=Aggregate, CN=Schema, CN=Configuration, DC=abc,DC=com

The biggest problem to date I've had with these PCs is
they take forever to log on.

Any thoughts on this?

Confused in Canada

 

[Guest]

Group policy may override your settings.

Take a look at this KB.
http://support.microsoft.com/default.aspx?kbid=294785

BR,
Denis

 

[Ace Fekay [MVP]]

In

Hello

We just recently changed our domain name from abc.com to
def.com for our internal network.

We now have a number of PCs that are registering in DHCP
as MachineName.abc.com instead of with the new DNS suffix.

When I IPCONFIG one of the PCs, it shows the Primary DNS
suffix as abc.com and the DNS Suffix Search list as
abc.com first, then def.com next.

I've looked in all the expected places for supplying this
suffix value, but everything is set as should be.

The affected PCs are all running W2K, connecting thru a
Server 2003 Domain Controller, are identical PCs (we have
a real mix in this shop!) and may have been installed
using RIS. I'm not sure on this last part as I'm new here.

I did a quick search of the registry on one PC and found
one setting for abc.com in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ADs\Providers\LDAP
\CN=Aggregate, CN=Schema, CN=Configuration, DC=abc,DC=com

The biggest problem to date I've had with these PCs is
they take forever to log on.

Any thoughts on this?

Confused in Canada

If you changed your domain name, then may I assume you disjoined and then
rejoined the machines to the new domain? If so, the default behavior of the
client machines is to change its Primary DNS Suffix to the new domain. The
Primary DNS Suffix can be manually changed in System Properties, Computer ID
tab. Or you can use a GPO as Dennis suggested.

Long logon times are indicative of using the wrong DNS servers, which you
may be inadvertenly using your ISP's DNS. The domain is found by querying
DNS. If you are using your ISP's DNS, its asking those/that server. They do
not have that answer, hence long logon times. Other things fail as well,
such as GPOs, and access denials while accesing folders, printers, etc. Just
use your internal DNS only. Configure a forwarder to your ISP's DNS in your
internal DNS server properties.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.