Not sure if DNS is set up correctly

  • Thread starter Thread starter Sam Story
  • Start date Start date
S

Sam Story

I'm new to windws 2000 and DNS and had a question.
Sometimes I feel like our two servers are not
communicating the way they should and I have nioticed that
all the workstations and 1 server are set up with
the "full computer name" as computername.SLSB.LOCAL, in
the SLSB.LOCAL domain. Our other server is set up with
the "full computer name" as computername.SLSB on the
SLSB.LOCAL domain. is this ok or should the second
server's full name be computername.SLSB.LOCAL?
Thanks
 
In
Sam Story said:
I'm new to windws 2000 and DNS and had a question.
Sometimes I feel like our two servers are not
communicating the way they should and I have nioticed that
all the workstations and 1 server are set up with
the "full computer name" as computername.SLSB.LOCAL, in
the SLSB.LOCAL domain. Our other server is set up with
the "full computer name" as computername.SLSB on the
SLSB.LOCAL domain. is this ok or should the second
server's full name be computername.SLSB.LOCAL?
Thanks
Click to expand...

As Eric mentioned, that server wasn't installed correctly. There is a script
that will fix this. Before I can email you the script, I need to verify that
this machine is a DC and that it is part of this domain and that truly the
Primary DNS Suffix is the problem here. If you can post an ipconfig /all
(unedited of course) that will help me determine if the script will help
you.

Thanks

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Here is the ipconfig /all from my workstation.
U:\ipconfig /all

Windows 2000 IP Configuration

Host Name...........: sstory
Primary DNS Suffix........: SLSB.LOCAL
Node Type...........: Hybrid
IP Routing Enabled.......: No
WINS Proxy Enabled.......: No
DNS Suffix Search List.......: SLSB.LOCAL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix..:
Description...........: 3Com 3c920 Integrated Fast
Ethernet Controller <3C905C-TX Compatible>
Physical Address........: 00-06-5B-A5-AD-AC
DHCP Enabled...........: No
IP Address............: 162.10.1.67
Subnet Mask............: 255.255.255.0
Default Gateway.........: 162.10.1.1
DNS Servers............: 162.10.1.251
Primary WINS Server.......: 162.10.2.251

U:\>
The server 162.10.2.251 is the one with just
computername.SLSB
 
In (e-mail address removed) <[email protected]> posted a
question
Then Kevin replied below:
Here is the ipconfig /all from my workstation.
U:\ipconfig /all

Windows 2000 IP Configuration

Host Name...........: sstory
Primary DNS Suffix........: SLSB.LOCAL
Node Type...........: Hybrid
IP Routing Enabled.......: No
WINS Proxy Enabled.......: No
DNS Suffix Search List.......: SLSB.LOCAL

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix..:
Description...........: 3Com 3c920 Integrated Fast
Ethernet Controller <3C905C-TX Compatible>
Physical Address........: 00-06-5B-A5-AD-AC
DHCP Enabled...........: No
IP Address............: 162.10.1.67
Subnet Mask............: 255.255.255.0
Default Gateway.........: 162.10.1.1
DNS Servers............: 162.10.1.251
Primary WINS Server.......: 162.10.2.251

U:\>
The server 162.10.2.251 is the one with just
computername.SLSB
Click to expand...

This is the wrong ipconfig, Ace needs to se the ipconfig for the DC to
verify The primary DNS suffix. The script will fix the DNS suffix but it
must be verified first.
 
In
Kevin D. Goodknecht said:
In (e-mail address removed) <[email protected]> posted a
question
Then Kevin replied below:

This is the wrong ipconfig, Ace needs to se the ipconfig for the DC to
verify The primary DNS suffix. The script will fix the DNS suffix but
it must be verified first.
Click to expand...

That's right. Need to see the ipconfig output from it first to make sure.

Also, now more confusing, Sam now says the other computer's NAME is SLSB, I
thought he said the Primary DNS Suffix is SLSB....hmmm.....gots to see that
ipconfig...


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
OK here is the ipconfig /all of the server That I believe
has a problem. Thanks
Windows 2000 IP Congfiguration
Host Name........: spooner1
Primary DNS Suffix......: SLSB
Node Type.........: Hybrid
IP Routing Enabled.....: Yes
WINS Proxy Enabled.....: No
DNS Suffix Search List.....: SLSB

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix...:SLSB
Description..........: Intel 8255x-based PCI
Ethernet Adapter <10/100>
Physical Address........: 00-B0-D0-AB-67-69
DHCP Enabled...........: No
IP Address............: 162.10.2.251
Subnet Mask............: 255.255.255.0
Default Gateway.........: 162.10.2.1
DNS Servers............: 162.10.1.251
Primary WINS Server.......: 162.10.2.251
 
In (e-mail address removed) <[email protected]> posted a
question
Then Kevin replied below:
OK here is the ipconfig /all of the server That I believe
has a problem. Thanks
Windows 2000 IP Congfiguration
Host Name........: spooner1
Primary DNS Suffix......: SLSB
Node Type.........: Hybrid
IP Routing Enabled.....: Yes
WINS Proxy Enabled.....: No
DNS Suffix Search List.....: SLSB

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix...:SLSB
Description..........: Intel 8255x-based PCI
Ethernet Adapter <10/100>
Physical Address........: 00-B0-D0-AB-67-69
DHCP Enabled...........: No
IP Address............: 162.10.2.251
Subnet Mask............: 255.255.255.0
Default Gateway.........: 162.10.2.1
DNS Servers............: 162.10.1.251
Primary WINS Server.......: 162.10.2.251
Click to expand...

As you can see you primary DNS suffix is SLSB which is at minimum a single
label domain name. However if your AD Domain name is SLSB.local then this is
a disjointed names for which I can provided you with a script developed for
MS Support Services to change the primary DNS suffix on a domain controller.
 
Our AD Domain name is SLSB.local, So if this script will
fix the problem, I would appreciate it if you could send
it to me with any instructions I need to run it. Thanks
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
Also this server sits at a different location and is
connected using a cisco router at each end. I'm not sure
if that makes a diffrence or not.
Thanks
 
In
Samuel Story said:
Also this server sits at a different location and is
connected using a cisco router at each end. I'm not sure
if that makes a diffrence or not.
Thanks
Click to expand...



Not in this case. Did you get the script?
 
I received the script and ran it. It did as you said and
corrected the server's name to the correct primary dns
suffix. Everything seems to be working ok. Thank you very
much for your help.
Sam
 
Back
Top