• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 387
  • Last Modified:

Mysterious case of DNS not getting entry update from DHCP for non Windows machine.

Hi,

I'm having mysterious issue that confused me for such a long time till now, I've got one DC which acted as DNS and DHCP as well. I'm using Windows Server 2003 R2 SP2 64 bit AD integrated for both DNS and DHCP server.

However it is successfully giving out IP address to all IP enabled device and machine but when updating the DNS entry, only the Windows machine (workstations and server) gets their IP registered in the DNS server, therefore i cannot ping and access the other Linux machine apart from using IP address only.

restarting the DNS (plus RELOAD the entry) and DHCP services doesn't help at all and also entering the DHCP assigned IP address into the DNS server caused more problem since the address is assigned to different host already by DHCP but not gets updated in the DNS server (only to non-windows machine).

If anyone know how to diagnose and help me solve this problem that'd be very great helps.

Thanks.
0
jjoz
Asked:
jjoz
  • 4
  • 2
  • 2
2 Solutions
 
Darius GhassemCommented:
Go to the Properties of the DNS zone make sure you have non-secure updates for DNS updates
0
 
jjozAuthor Commented:
"non-secure updates" --> does this applies to the workstation or to the other DNS server type eg. BIND server ?
0
 
jjozAuthor Commented:
ok, I've changed the Dynamic Updates into "Nonsecure and secure" is that what you mean ?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Darius GhassemCommented:
Yes, that is what I mean this allows non windows clients to update
0
 
Chris DentPowerShell DeveloperCommented:

If DHCP is updating DNS the updates (all updates) are Secure and the client will not be permitted to update DNS directly. If that is the case, please re-enable secure updates.

However:

If your client does not have a DNS Suffix the record has no where in DNS to go. All clients must have a DNS Suffix listed in DHCP matching your Forward Lookup Zone name or they will not register.

Chris
0
 
jjozAuthor Commented:
ah... you could be right Chris, "All clients must have a DNS Suffix listed in DHCP matching"
so in this case when I name the non Windows machine i must put FFQDN eg. newLinux.domain.com ?

apart from changing the Dynamic Updates into "Nonsecure and secure" mode ?
0
 
Chris DentPowerShell DeveloperCommented:

Yep, that's right.

Then DHCP will post the full name into DNS for you (allowing you to continue using Secure Updates).

Chris
0
 
jjozAuthor Commented:
thanks man for your reply.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now