We help IT Professionals succeed at work.

New podcast episode! Our very own Community Manager, Rob Jurd, gives his insight on the value of an online community. Listen Now!

x

Windows Server 2003, DHCP update DNS, PTR ok but A not set

ptr727
ptr727 asked
on
1,559 Views
Last Modified: 2012-06-27
I am trying to set up a small home network using Windows Server 2003 R2 x64 for DNS and DHCP.
I want the DHCP server to always update the A and PTR records for any client that is issued a DHCP address.
I want to support XP, vista, Linux and Mac machines, thus I do not want to disable NetBIOS and have the DNS server be able to resolve all host names.

W2K3 R2 Server configured standalone, called server.home, workgroup home.
Server is static 10.0.0.20, gateway 10.0.0.1, DNS pointing to itself 10.0.0.20
Router address is 10.0.0.1

Q: Is it advisable to point the server static IP DNS configuration to itself?

I configured the DNS and DHCP options as follows:
DHCP scope is 10.0.0.33 to 10.0.0.128
DHCP set to enable dynamic updates, always update, discard when lease expires, and dynamically update hosts that do not support dynamic updates.
DNS forward scope is home, reverse for 10.0.0
DNS server set to allow both secure and insecure updates.

When a XP client, called xp.home, gets an IP from DHCP, the reverse zone gets a PTR registration, but there is no A record for xp.home

I tested similar configurations using W2K3 R2 x64 and Server 2008 RC0 x64.

Q: Any ideas why the PTR would update but not the A, and how do I solve this?

Regards
P.
Comment
Watch Question

Consider setting up a domain account to use for updating records in DHCP.  Sounds like a permission issue.  Right Click DHCP server......
Brian PiercePhotographer
CERTIFIED EXPERT
Awarded 2007
Top Expert 2008

Commented:

Author

Commented:
I am running in standalone server mode, no domains.
I have the DNS server set to not require authorization.

And if it was a permission issue, why would the PTR update but not the A, unless the client does that and not the DHCP server?

Author

Commented:
KCTS: I did configure DHCP to update DNS.
Quote from original text: "DHCP set to enable dynamic updates, always update, discard when lease expires, and dynamically update hosts that do not support dynamic updates."
PowerShell Developer
CERTIFIED EXPERT
Top Expert 2010
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Chris, the PTR registration is xp.home, and I can reverse lookup the IP.
The KB sounds interesting, I'll change the configuration to a multi level domain and report back.

On DNS sub domain configuration, if I have a domain say foo.com that is hosted by a provider, can I just configure my home DNS to be home.foo.com without needing to configure anything with the foo.com provider?

Regards
P.
Chris DentPowerShell Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:

That's correct, yes.

foo.com doesn't need to know about home.foo.com unless you expect to resolve names within home.foo.com over the Internet.

Chris

Author

Commented:
Chris, thanks, multi level domain solved the problem.
Chris DentPowerShell Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:

Great stuff, glad I could help out.

Chris
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.