2000 DHCP updates WINS but not DNS

[Guest]

Hello,

Our DHCP server is issuing leases, and puting the entries into WINS, but not
into DNS. I do DHCP setup to update DNS. Anyone seen this b4?

Greg

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Hello,

Our DHCP server is issuing leases, and puting the entries
into WINS, but not into DNS. I do DHCP setup to update
DNS. Anyone seen this b4?

Greg

You have to enable option 015 with the domain name, enable DNS updates by
right clicking on the DHCP server, choose properties, then on the DNS tab.
Also, the DHCP server machine must have the DDNS server IP in TCP/IP
properties on the NIC.

 

[Guest]

I do have all those setting setup correctly. That is the problem. Everything
seems to be setup right, but DNS is not recieving updates. any more ideas?

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I do have all those setting setup correctly. That is the
problem. Everything seems to be setup right, but DNS is
not recieving updates. any more ideas?

Is the DHCP client service running?
The DHCP client service is required for DNS registration, even if the client
is static.

One more thing, is the domain a single-label domain name?

 

[Herb Martin]

Also note this:

DHCP does NOT update WINS (only the
clients do that.)

DHCP server must have the scope configured
with the DNS zone name (otherwise how would
it know which zone to register in), the DHCP
server must be able to FIND the "master" (usually
the Primary or equivalent DNS server for that
zone.)

DNS server must be set to dynamic for the zone.

If set to Secure Only the DHCP server must be
IN the DOMAIN and must be authentication.


Check you DNS in general:


--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

 

[Graham Banks]

I also can't get DNS to be automatically updated. I'm trying to get hosts on a
LAN to resolve each other's names.

I've tried it with a Windows 2000 domain and without (i.e. with Active
Directory on and off). In both cases, the DNS service works (the hosts resolve
each other's names if I manually enter a host in the DNS service's control
applet), the DHCP service works, the DNS zone is set to accept dynamic updates,
the DHCP server is set to update DNS (with all the "cover all" options set),
the scope has the right domain as the DNS Domain name (I've also named the
scope the same as the name of the DNS domain name), the DNS and DHCP services
run on the same computer and the DNS server for the network connection is set
to 127.0.0.1.

According to the tutorial I've followed, I've done everything necessary.

Any other ideas?

TIA

Graham