New 2K3 DC on 2K Domain

Hi everybody:
I used to have one single 2K DC in my network. I just got
2 new boxes that came 2K3 precharged. I've already
promoted one of them to DC and made it GC. I added DNS
server role to the new one and nothing happend, then I
realized the old DC wasn't configured as AD integrated, I
changed and the zone replicated to the new one. Now I'm
getting somewhat weird in the new one: when I start
nslookup it says "Default Server: unknown / Address:
x.x.x.x (this new dns address)>", even so, I can resolve
any internal and external hosts. My concern is if I can
leave it as it is, I'm planning to demote the 2K DC (of
course after pointing my clients to the new one), will
this affect my clients when I turn off the old one?
In the new one I was getting event ID 13508 on FRS once a
day, it stopped two days ago and the event ID 13509 never
came up, any ideas?
The old one is also WINS server, can I have to WINS
servers at any given time? How can assign this role to the
new 2K3 one and remove it from the old 2K one?
Sorry for this long post.
Any help would be appreciated.

Gux.

It just means that DNS cannot resolve the IP address of the DNS server to
its name. If you want it to display a name, make sure there is an entry for
it in the reverse lookup zone for that IP subnet.

"Gux" <(E-Mail Removed)> wrote in message
news:220501c4700b$a0929a50$(E-Mail Removed)...
> Hi everybody:
> I used to have one single 2K DC in my network. I just got
> 2 new boxes that came 2K3 precharged. I've already
> promoted one of them to DC and made it GC. I added DNS
> server role to the new one and nothing happend, then I
> realized the old DC wasn't configured as AD integrated, I
> changed and the zone replicated to the new one. Now I'm
> getting somewhat weird in the new one: when I start
> nslookup it says "Default Server: unknown / Address:
> x.x.x.x (this new dns address)>", even so, I can resolve
> any internal and external hosts. My concern is if I can
> leave it as it is, I'm planning to demote the 2K DC (of
> course after pointing my clients to the new one), will
> this affect my clients when I turn off the old one?
> In the new one I was getting event ID 13508 on FRS once a
> day, it stopped two days ago and the event ID 13509 never
> came up, any ideas?
> The old one is also WINS server, can I have to WINS
> servers at any given time? How can assign this role to the
> new 2K3 one and remove it from the old 2K one?
> Sorry for this long post.
> Any help would be appreciated.
>
> Gux.

Thanks for your help, Bill. This issue is now fixed.
Gux.

>-----Original Message-----
> It just means that DNS cannot resolve the IP address
of the DNS server to
>its name. If you want it to display a name, make sure
there is an entry for
>it in the reverse lookup zone for that IP subnet.
>
>"Gux" <(E-Mail Removed)> wrote in message
>news:220501c4700b$a0929a50$(E-Mail Removed)...
>> Hi everybody:
>> I used to have one single 2K DC in my network. I just
got
>> 2 new boxes that came 2K3 precharged. I've already
>> promoted one of them to DC and made it GC. I added DNS
>> server role to the new one and nothing happend, then I
>> realized the old DC wasn't configured as AD integrated,
I
>> changed and the zone replicated to the new one. Now I'm
>> getting somewhat weird in the new one: when I start
>> nslookup it says "Default Server: unknown / Address:
>> x.x.x.x (this new dns address)>", even so, I can resolve
>> any internal and external hosts. My concern is if I can
>> leave it as it is, I'm planning to demote the 2K DC (of
>> course after pointing my clients to the new one), will
>> this affect my clients when I turn off the old one?
>> In the new one I was getting event ID 13508 on FRS once
a
>> day, it stopped two days ago and the event ID 13509
never
>> came up, any ideas?
>> The old one is also WINS server, can I have to WINS
>> servers at any given time? How can assign this role to
the
>> new 2K3 one and remove it from the old 2K one?
>> Sorry for this long post.
>> Any help would be appreciated.
>>
>> Gux.
>
>
>.
>