"Monster" <Monster@gmail.com> wrote in message
news:0403b381-93ed-4910-bf4c-5823a0dee941@d21g2000prf.googlegroups.com...
> Hi,
>
> I have a strange issue.
> Sometimes when i'm trying to connect to a webpage
> http://www.marktplaats.nl
> i get an error.

We all do -- sometimes.

> Here's my configuration
>
> Windows 2003 domain controller running DNS.
> Client PC getting IP config by DHCP.
> Primairy DNS is my domain controller wich runs DNS

Clients don't know about "primary" (or 'secondary') for resolving
DNS names. They use a Preferred and perhaps Alternates which
must ALL be INTERNAL DNS servers.

> Gateway is my router / Modem wich is connected to the internet.
>
> When i reboot my domain controller the issue is fixed but i don't feel
> good having to reboot my domain controller every time a webpage is not
> accesible.

You haven't described the actual issue or problem...?

What happens exactly? What happens when you test with NSLOOKUP
both bare and with a specific DNS server specified? Check against EVERY
DNS server configured to be used by the client(s):

nslookup www.marktplaats.nl OPTIONAL.DNSServer.IP.ADDRESS

Work through all the DNS servers the client might use.

How does your DC resolve EXTERNAL Names?


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com (phone on web site)

If you use LinkedIn then tell me where you know me from when linking:

http://www.linkedin.com/in/herbmartin