Hosts not showing up in DNS Forward Lookup Zone

[plsntn rules]

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

thanks for any help

 

[Herb Martin]

Just finsished setting up a new AD environment and

everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

[It is sort of irrelevant to claim "correct DNS settings" if you don't
post them when your system is not working properly?!?]

Try ENABLING Dynamic updates on the ZONE you wish to automate,
then MAKE SURE each CLIENT and SERVER uses your DNS system
in it's NIC properties -- finally, if any of this changes, run these
commands:

On NON-DCs: ipconfig /registerDNS

On DCs: Net Stop DNS
Net Start DNS

(Remember, even the DNS server DC needs to be a CLIENT OF ITSELF.)

 

[plsntn rules]

Dynamic Updates ARE enabled on the DNS server.
I am using static IPs and not DHCP.

I tried the commands you provided and still no go...

And yes each CLIENT and SERVER is using the same DNS
settings.
Any other suggestions?

thanks..

-----Original Message-----

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

[It is sort of irrelevant to claim "correct DNS settings" if you don't
post them when your system is not working properly?!?]

Try ENABLING Dynamic updates on the ZONE you wish to automate,
then MAKE SURE each CLIENT and SERVER uses your DNS system
in it's NIC properties -- finally, if any of this changes, run these
commands:

On NON-DCs: ipconfig /registerDNS

On DCs: Net Stop DNS
Net Start DNS

(Remember, even the DNS server DC needs to be a CLIENT OF ITSELF.)

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

thanks for any help

.

 

[plsntn rules]

I am using static IPs on the members and servers.
Do I need to have the DHCP Client Service enabled and
running to have the Dynamic DNS Update to work?

I enabled it and did a Ipconfig /refreshdns and VOILA! the
memeber showed up in the forward zone lookup list.

But I really dont want to generate additional DHCP
traffice because we do not have a DHCP server on our
network.

Is the DHCP Client Service a requirement for dynamic dns
updates even on machines with static IPs?

thanks for any help..

-----Original Message-----
Dynamic Updates ARE enabled on the DNS server.
I am using static IPs and not DHCP.

I tried the commands you provided and still no go...

And yes each CLIENT and SERVER is using the same DNS
settings.
Any other suggestions?

thanks..

-----Original Message-----

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

[It is sort of irrelevant to claim "correct DNS

settings"
if you don't

post them when your system is not working properly?!?]

Try ENABLING Dynamic updates on the ZONE you wish to automate,
then MAKE SURE each CLIENT and SERVER uses your DNS system
in it's NIC properties -- finally, if any of this changes, run these
commands:

On NON-DCs: ipconfig /registerDNS

On DCs: Net Stop DNS
Net Start DNS

(Remember, even the DNS server DC needs to be a CLIENT

OF

ITSELF.)





.

.

 

[Herb Martin]

I am using static IPs on the members and servers.

Do I need to have the DHCP Client Service enabled and
running to have the Dynamic DNS Update to work?

Yes, the DHCP Client service does the REGISTRATION for
dynamic DNS.

(You need it EVEN if you don't USE the actual DHCP feature.)

I enabled it and did a Ipconfig /refreshdns and VOILA! the
memeber showed up in the forward zone lookup list.

But I really dont want to generate additional DHCP
traffice because we do not have a DHCP server on our
network.

What DHCP traffic? You have the clients manually assigned so
they do no "dhcp traffic."

 

[Kevin D. Goodknecht Sr. [MVP]]

In plsntn rules <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply inline.

I am using static IPs on the members and servers.
Do I need to have the DHCP Client Service enabled and
running to have the Dynamic DNS Update to work?

Absolutely yes DHCP client service is required for DDNS

I enabled it and did a Ipconfig /refreshdns and VOILA! the
memeber showed up in the forward zone lookup list.

But I really dont want to generate additional DHCP
traffice because we do not have a DHCP server on our
network.

Is the DHCP Client Service a requirement for dynamic dns
updates even on machines with static IPs?

thanks for any help..

-----Original Message-----
Dynamic Updates ARE enabled on the DNS server.
I am using static IPs and not DHCP.

I tried the commands you provided and still no go...

And yes each CLIENT and SERVER is using the same DNS
settings.
Any other suggestions?

thanks..

-----Original Message-----
Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

[It is sort of irrelevant to claim "correct DNS settings" if you
don't post them when your system is not working properly?!?]

Try ENABLING Dynamic updates on the ZONE you wish to automate,
then MAKE SURE each CLIENT and SERVER uses your DNS system
in it's NIC properties -- finally, if any of this changes, run these
commands:

On NON-DCs: ipconfig /registerDNS

On DCs: Net Stop DNS
Net Start DNS

(Remember, even the DNS server DC needs to be a CLIENT OF ITSELF.)


Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

thanks for any help


.

.

 

[Herb Martin]

Are the clients all set with the same domain name as the ZONE
(the one marked for dynamic updates)? They register in their "own"
zone.

If this is the case, turn on logging for updates, use the commands to
provoke re-registration and review the log.

Double-check the DNS-ip settings the clients use -- if they are not
finding the RIGHT dns server (set).

Use nslookup (without specifying a DNS server) from the clients
to ensure they default to the right DNS server and are preferring it.

Dynamic Updates ARE enabled on the DNS server.
I am using static IPs and not DHCP.

I tried the commands you provided and still no go...

And yes each CLIENT and SERVER is using the same DNS
settings.
Any other suggestions?

thanks..

-----Original Message-----

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

[It is sort of irrelevant to claim "correct DNS settings" if you don't
post them when your system is not working properly?!?]

Try ENABLING Dynamic updates on the ZONE you wish to automate,
then MAKE SURE each CLIENT and SERVER uses your DNS system
in it's NIC properties -- finally, if any of this changes, run these
commands:

On NON-DCs: ipconfig /registerDNS

On DCs: Net Stop DNS
Net Start DNS

(Remember, even the DNS server DC needs to be a CLIENT OF ITSELF.)

Just finsished setting up a new AD environment and
everything seems to be working ok with the exception of
hosts are not being added to the DNS Forward Lookup Zone.

Am I missing something?

Both the member machines and the Domain controller have
the correct DNS settings...

thanks for any help

.