N
NetGear
Hi,
I have a test w2k AD domain with about 5 w2k clients.
Everything seems to be fine by the dns server side. The clients can logon to
the domain very fast and there is no dns errors in the event logs. The AD
looks and feels to work well. The automatic dynamic dns registration of the
clients fails, however.
If I type ipconfig /registerdns in cmd window, the clients A record shows up
immediately in the dns server. However, the PTR record is not updated,
although I have created the reverse lookup zone for my domain.
There is only one internal dns server address in each workstations tcp/ip
settings. The forwarders work very well.
How long should I typically wait for clients ddns registration and what can
cause that the automatic registration fails?
I have a test w2k AD domain with about 5 w2k clients.
Everything seems to be fine by the dns server side. The clients can logon to
the domain very fast and there is no dns errors in the event logs. The AD
looks and feels to work well. The automatic dynamic dns registration of the
clients fails, however.
If I type ipconfig /registerdns in cmd window, the clients A record shows up
immediately in the dns server. However, the PTR record is not updated,
although I have created the reverse lookup zone for my domain.
There is only one internal dns server address in each workstations tcp/ip
settings. The forwarders work very well.
How long should I typically wait for clients ddns registration and what can
cause that the automatic registration fails?