In news:47937383$0$5247$bf4948fe@news.tele2.nl,
Rik G. <q@q.nl> typed:

> Thanks for the extensive reply, Ace. And apologies for not providing
> config info.
>
> I've found where the "rub" was though. My DC has no DHCP service
> running. I use the router for that. This means the client
> workstations did not register properly in the DC's DNS. Checking "Use
> this connection's DNS suffix in DNS registration" on the workstations
> did the trick. The clients now properly register in the DC's DNS.
>
> My next question now is which Group Policy can force this option on
> the clients? The documentation (clicking with the question mark on
> this checkbox) says there should be a Group Policy which overrides
> the local setting, so I know this can be forced using Group Policy.
>
> Regards
>
> R.

You are welcome, Rik. The DHCP service I mentioned was the client service on
the DC. Despite it's name, it's actually the resolver service and if
disabled, the DC can't even resolve DNS names.

Good taht you changed to the DC's DHCP server service for DHCP services for
your clients. The router's is very limited in terms of certain features,
such as Dynamic Updates (actually called Option 081 that routers do not
support).

Marcin has the answer for your GPO question. If you have any more questions,
don't hesitate to post.

Ace