DHCP suffix issue

Hello All,

Not sure if this is the best place to post this question.

I don't believe this issue is affecting performance, but it looks odd. I
have windows 2003 server as a primary dc running dns and dhcp. Our domain
name is xyz.local
We have XP machines not part of the domain with a dns suffix xyz.com.

Now, after I join one of those XP machines to the domain and get ip through
dhcp, I see in the dhcp lease section, xpmachine.xyz.com where I should see
xpmachine.xyz.local

Also, when I run ipconfig/all on those workstations the results list both
dns suffix
xpmachine.xyz.local
xpmachine.xyz.com


So, is there a way to flush whatever was there in dhcp before it joined the
domain?
Will this clear itself up when the dhcp lease renews?


TP

There are several DNS suffixes that can be configured in Windows.
1: Primary DNS suffix. This is configured via System Properties -->
Computer Name --> Change --> More --> Primary DNS Suffix
2: Connection specific DNS suffix. This is either configured on the DNS tab
of the TCP/IP properties dialogue for each network adapter or is received
from DHCP

It sounds like you have xyz.com as the primary suffix and xyz.local as the
connection specific suffix or vice versa.

Incidentally this is how the Windows Firewall GPO works out whether to apply
the Domain profile or the Standard profile, based on the connection specific
DNS suffix. If it matches the Domain name then it assumes you are on the
Domain and otherwise it applies the Standard profile.

Cheers,
Jeremy.
"TP" <(E-Mail Removed)> wrote in message
news:E3DFC06A-2001-4218-BAC8-(E-Mail Removed)...
> Hello All,
>
> Not sure if this is the best place to post this question.
>
> I don't believe this issue is affecting performance, but it looks odd. I
> have windows 2003 server as a primary dc running dns and dhcp. Our domain
> name is xyz.local
> We have XP machines not part of the domain with a dns suffix xyz.com.
>
> Now, after I join one of those XP machines to the domain and get ip
> through
> dhcp, I see in the dhcp lease section, xpmachine.xyz.com where I should
> see
> xpmachine.xyz.local
>
> Also, when I run ipconfig/all on those workstations the results list both
> dns suffix
> xpmachine.xyz.local
> xpmachine.xyz.com
>
>
> So, is there a way to flush whatever was there in dhcp before it joined
> the
> domain?
> Will this clear itself up when the dhcp lease renews?
>
>
> TP
>

Jeremy,

I overlooked the tcp properties. There was an empty box for [use this dns
connection suffix], I filled it in and now we're looking good.

Thanks,
TP

"Jeremy" wrote:

> There are several DNS suffixes that can be configured in Windows.
> 1: Primary DNS suffix. This is configured via System Properties -->
> Computer Name --> Change --> More --> Primary DNS Suffix
> 2: Connection specific DNS suffix. This is either configured on the DNS tab
> of the TCP/IP properties dialogue for each network adapter or is received
> from DHCP
>
> It sounds like you have xyz.com as the primary suffix and xyz.local as the
> connection specific suffix or vice versa.
>
> Incidentally this is how the Windows Firewall GPO works out whether to apply
> the Domain profile or the Standard profile, based on the connection specific
> DNS suffix. If it matches the Domain name then it assumes you are on the
> Domain and otherwise it applies the Standard profile.
>
> Cheers,
> Jeremy.
> "TP" <(E-Mail Removed)> wrote in message
> news:E3DFC06A-2001-4218-BAC8-(E-Mail Removed)...
> > Hello All,
> >
> > Not sure if this is the best place to post this question.
> >
> > I don't believe this issue is affecting performance, but it looks odd. I
> > have windows 2003 server as a primary dc running dns and dhcp. Our domain
> > name is xyz.local
> > We have XP machines not part of the domain with a dns suffix xyz.com.
> >
> > Now, after I join one of those XP machines to the domain and get ip
> > through
> > dhcp, I see in the dhcp lease section, xpmachine.xyz.com where I should
> > see
> > xpmachine.xyz.local
> >
> > Also, when I run ipconfig/all on those workstations the results list both
> > dns suffix
> > xpmachine.xyz.local
> > xpmachine.xyz.com
> >
> >
> > So, is there a way to flush whatever was there in dhcp before it joined
> > the
> > domain?
> > Will this clear itself up when the dhcp lease renews?
> >
> >
> > TP
> >
>

Can I suggest you add this as an option in DHCP, this would provide you with
a single management point.

"TP" <(E-Mail Removed)> wrote in message
news:5AAA43DE-5376-4165-81E9-(E-Mail Removed)...
> Jeremy,
>
> I overlooked the tcp properties. There was an empty box for [use this dns
> connection suffix], I filled it in and now we're looking good.
>
> Thanks,
> TP
>
> "Jeremy" wrote:
>
>> There are several DNS suffixes that can be configured in Windows.
>> 1: Primary DNS suffix. This is configured via System Properties -->
>> Computer Name --> Change --> More --> Primary DNS Suffix
>> 2: Connection specific DNS suffix. This is either configured on the DNS
>> tab
>> of the TCP/IP properties dialogue for each network adapter or is received
>> from DHCP
>>
>> It sounds like you have xyz.com as the primary suffix and xyz.local as
>> the
>> connection specific suffix or vice versa.
>>
>> Incidentally this is how the Windows Firewall GPO works out whether to
>> apply
>> the Domain profile or the Standard profile, based on the connection
>> specific
>> DNS suffix. If it matches the Domain name then it assumes you are on the
>> Domain and otherwise it applies the Standard profile.
>>
>> Cheers,
>> Jeremy.
>> "TP" <(E-Mail Removed)> wrote in message
>> news:E3DFC06A-2001-4218-BAC8-(E-Mail Removed)...
>> > Hello All,
>> >
>> > Not sure if this is the best place to post this question.
>> >
>> > I don't believe this issue is affecting performance, but it looks odd.
>> > I
>> > have windows 2003 server as a primary dc running dns and dhcp. Our
>> > domain
>> > name is xyz.local
>> > We have XP machines not part of the domain with a dns suffix xyz.com.
>> >
>> > Now, after I join one of those XP machines to the domain and get ip
>> > through
>> > dhcp, I see in the dhcp lease section, xpmachine.xyz.com where I
>> > should
>> > see
>> > xpmachine.xyz.local
>> >
>> > Also, when I run ipconfig/all on those workstations the results list
>> > both
>> > dns suffix
>> > xpmachine.xyz.local
>> > xpmachine.xyz.com
>> >
>> >
>> > So, is there a way to flush whatever was there in dhcp before it joined
>> > the
>> > domain?
>> > Will this clear itself up when the dhcp lease renews?
>> >
>> >
>> > TP
>> >
>>