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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, I've changed the Dynamic Updates into "Nonsecure and secure" is that what you mean ?
Yes, that is what I mean this allows non windows clients to update
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 ?
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 ?
Yep, that's right.
Then DHCP will post the full name into DNS for you (allowing you to continue using Secure Updates).
Chris
ASKER
thanks man for your reply.
ASKER