Setting up DNS - Newbie question

  • Thread starter Thread starter Fran
  • Start date Start date
F

Fran

I posted a message earlier. I need to clarify some things:

1) This is a Windows 2000 Server , SP4, AD domain
2) It's the PDC
3) It's NOT the DHCP server (another server on the same subnet handles
this for another company and our system.)
4) the DHCP server does not have DNS running (it is using the ISP's
DNS servers)

This is a small server running on an AMD/XP box handling 10 users, 1gb
RAM, 2.6 Ghz CPU on an ASUS A7N8X-Deluxe MB with a SATA Raid.

From time to time I get the following problems:

1) Workstations will not be able to connect to the server. This hasn't
happened DURING work but apparently at night. Happened twice in past 4
weeks. Turning the server off and restarting fixes the problem. I've
tried IPCONFIG /FLUSHDNS but that doesn't help, nore does simply
restarting Windows 2000 Server.

2) Almost daily Backup Exec and/or Pervasive database will lose
connection to its service (service just stops running occasionally
giving error 7031). Most of the time I have to restart the server,
although there are SOME instances where I can connect remotely and
restart them. (Backup Exec ver. 9.1 and Pervasive 2000i)

I have run diagnostics on the hardware and all tests report OK.

These problems don't happen EVERY day but MOST days (yes, thare are
SOME days where everything just runs great all day long.) It has been
driving me nuts trying to isolate WHY these problems happen.

Could these issues (DNS and the loss of these services) be related?
 
4) the DHCP server does not have DNS running (it is using the ISP's
DNS servers)

What about YOUR DNS server? Who is that using for DNS? What I'm getting at
is this: in your AD environment, use YOUR DNS server for EVERYTHING (clients
and servers). Don't point to your ISP's server for anything. Try this.
Reboot your servers, just to be sure. Then if the problem still persists,
post more information regarding your setup.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
In
Fran said:
I posted a message earlier. I need to clarify some things:

1) This is a Windows 2000 Server , SP4, AD domain
2) It's the PDC
3) It's NOT the DHCP server (another server on the same subnet handles
this for another company and our system.)
4) the DHCP server does not have DNS running (it is using the ISP's
DNS servers)

This is a small server running on an AMD/XP box handling 10 users, 1gb
RAM, 2.6 Ghz CPU on an ASUS A7N8X-Deluxe MB with a SATA Raid.

From time to time I get the following problems:

1) Workstations will not be able to connect to the server. This hasn't
happened DURING work but apparently at night. Happened twice in past 4
weeks. Turning the server off and restarting fixes the problem. I've
tried IPCONFIG /FLUSHDNS but that doesn't help, nore does simply
restarting Windows 2000 Server.

2) Almost daily Backup Exec and/or Pervasive database will lose
connection to its service (service just stops running occasionally
giving error 7031). Most of the time I have to restart the server,
although there are SOME instances where I can connect remotely and
restart them. (Backup Exec ver. 9.1 and Pervasive 2000i)

I have run diagnostics on the hardware and all tests report OK.

These problems don't happen EVERY day but MOST days (yes, thare are
SOME days where everything just runs great all day long.) It has been
driving me nuts trying to isolate WHY these problems happen.

Could these issues (DNS and the loss of these services) be related?
Click to expand...


Fran, just want to clarify, and Deji and Lanwench already stipulated the
empirical rule with AD:
DO NOT USE YOUR ISP's DNS SERVER on any AD member (clients and DCs).

You'll need to follow this to eliminate your errors.

Otherwise, as you;ve experienced, numerous errors.

So about your DHCP server, as has been already asked, why are you using
their server? If you only have 10 users, and their server is on your subnet
for DHCP, and their DHCP's Scope Option 006 is giving the clients the ISP's
DNS, then we now both know that is detrimental to your AD environment. If
only 10 users, I would highly suggest to use static addressing if you can't
get the right DNS addresses to be given to your clients or you will continue
to have major problems.

Backup Exec is probably dumping because of authentication and it;s using an
AD account for that and that all points back to using the incorrect DNS. THe
DNS that is hosting your AD zone name is the only DNS that you need to use
in your environment. As Lanwench said in the other thread, use a Forwarder
for efficient Internet resolution.

btw- there is no such thing as a PDC in AD. There;'s a role function that
equates to what an NT4 PDC did, plus other functions it performs (time
synch, password synch, etc) but it is not a "PDC".

Tell you what, if the other company has an AD domain, I bet their having
problems as well due to the DNS addresses the DHCP is dishing out. Maybe you
and them can compromise if you want with DHCP and DNS. If they are running
AD as well, then that means they have a DNS server with their AD info. IF
this is the case, you can create a secondary zone on their DNS of your AD
zone, and have Option 006 set to only their DNS and everything will work
fine.

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
I suppose there's NO reason I couldn't get off of their net by
assigning static IP addresses. I didn't think of that but then I just
got this acct, too.

Thanks for the DNS info, too! THis is great to know! I'll be fixing
that this week.

Fran
 
In
Fran said:
I suppose there's NO reason I couldn't get off of their net by
assigning static IP addresses. I didn't think of that but then I just
got this acct, too.

Thanks for the DNS info, too! THis is great to know! I'll be fixing
that this week.

Fran
Click to expand...


If there's not that many users, maybe static will do fine, or segment them
by putting a router between them on their own subnet.

Here's some pointers with an FAQ on AD and DNS:
http://support.microsoft.com/?id=291382

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
I don't have much experience with creating subnets. I'll look into
this, too. Something I should know ;)

Thanks!

Fran
 
In
Fran said:
I don't have much experience with creating subnets. I'll look into
this, too. Something I should know ;)

Thanks!

Fran
Click to expand...


Good luck with everything!

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top