Windows Forum

Ask something
Discussion Locked

Dynamic DNS doesn't update forward zone

0 helpful
17 replies

by robcoxon 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running DNS on a W2K server setup as the DC. DNS on this server is only used for the intranet. Internet DNS is performed by our ISP through ISA server. I have a standard primary zone setup for the forward and reverse lookup zones. I have the allow dynamic updates box checked on both. The reverse zone works great but the forward zone will not post any updates dynamically.

17 replies

by voldar

You have a W2k server, so this is having an AD structure also. What about the DHCP in your LAN? Are the clients (computers) DHCP enabled, or static IP addresses. The forward lookup zone coverts names to IP addresses, while the reverse lookup zone converts the IP to names. So, this is why any computer that joins your network have also a record in the reverse lookup zone. The problem with the forward lookup zone consist of the fact that maybe your clients are running computers with W9x or any other below the W2K, and they are not able to interact with the DNS for dynamicaly update. You should set up (if you have not) a DHCP server to allways update the A and the PTR records for those clients.

by voldar

Yes, I see, but is your DHCP server set up to perform dynamic updates of the DNS records?!!?

by robcoxon

Yes, DHCP is set up to perform dynamic updates. The reverse lookup zone is functional.

by voldar

If u use from a client computer the
ipconfig /registerdns command
does this client register to your DNS forward lookup zone? If u flushdns also, does the client re-register itself on the DNS?
And, last, but not least, is the DNS address (where u want the clients to register) the first DNS address on your TCP/IP configuration? Because if it is not, you'll not have DNS records in your DNS Forward lookup zone.

by wroming

Ok this is a pretty broad spectrum question but, here it goes: If you have questions after this please feel free to email me at wroming@ci.killeen.tx.us

DNS on Server Side make sure that you are allowing zone transfers with your ISP servers. Now under the properties of your Server this is what you need to make sure you have
1. Interfaces: Listen on all interfaces
2. Forwarders: If you have a external DNS have it set to forward to it. If you do not only your ISP does then have it set to forward to those ISP's DNS servers
3. Advanced: Most of that is defaulted and already setup
4. Root Hints: Make sure your DNS server is learning the ROOT servers for the net.
5.Logging: N/A no need for what you are wanting to do.
6. Montoring: again N/A except for when you are troubleshooting but, the dos way in my opinion is better.
7. Security: Make sure all the admin groups have full control and that the Authencated users have read access; also allow inhertiable permissions on the security tab.

*****NOTE******Will have to make a second post to complete the answer will only let me have certain amount of space.

by wroming

Now moving on to the Forward lookup Zone you created.

1. General: Make sure you have dynamic updates set to yes also check your status is running and type is Active Directory-Intregrated
2. SOA: Most of the time the default is fine here
3. Name Servers: Make sure that you have all your names server in here added.
4. WINS: If you are using WINS make sure your servers are added here as well as using WINS forward lookup check box is checked.
5. Zone Transfers: Allow to any server is checked
6. Security: Once again on Security the security needs to be the same as above.

Now for the DHCP:

Under the properties for the DHCP server this is what needs to be there. We are only concerned with the DNS tab for this area.

DNS: The first two check boxes need to be checked for allow DNS updates and disgard information after lease expires. Also, make sure that Always update DNS information is selected.
Scope Options: Make sure that your scope options has all the information required DNS as well as WINs if you are using it, gateway, domain name

Now to the clients:

The only settings that needs to be there is the following:

Under your network properties of TCP-IP make sure that your IP and DNS information is handled by the DNS information. Afterwards you can do the following from a command prompt done in that order.

ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
nbtstat -RR

by wroming

The commands for the local user is done to flush out any DNS and/or WINS information that is conflicting with your settings. Be sure that you type the commands exact because the nbtstat commands are case sensitive. Once again if you have any questions, comments and/or concerns please feel free to contact me at wroming@ci.killeen.tx.us

This discussion is closed to new replies.