Mark
asked on
SBS2008 DHCP not updating DNS
I have a Linux host in my SBS2008 domain that get its DHCP address from the SBS2008 server (see underlined entry in DHCP image). However, it does not put the DHCP IP into the DNS list so other hosts cannot get to it (see DNS image). I know I can put a static IP into the DNS list for this host, but I'd rather use DHCP. For DHCP > IPv4 Properties > DNS, I have "Enable DNS dynamic updates according to the settings below:", "Always dynamically update DNS A and PTR records", "Discard A and PTR records when lease is deleted", and "Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0)". I also have DHCP > IPv4 Properties > Advanced > Credentials, set with the administrator ID and password.
What do I need to do to get this host into DNS (host 192.168.0.50 is another Linux host showing up in the DHCP leases, but not in the DNS)
DHCP.jpg
DNS.jpg
What do I need to do to get this host into DNS (host 192.168.0.50 is another Linux host showing up in the DHCP leases, but not in the DNS)
DHCP.jpg
DNS.jpg
Miguel Angel Perez Muñoz
try configuring DHCP to register hosts on DNS: http://technet.microsoft.com/en-us/library/cc787034(WS.10).aspx
ASKER
Yes, as stated in my initial post, I already have "Always dynamically update DNS A and PTR records" set, but it's not doing it. The DHCP lease obviously does have both the IP and the hostname, so I'm puzzled as to why it is not updating the DNS.
Have you marked force update records? have you provided adequate user with privileges?
ASKER
Sorry for the delay ...
Drashiel: > Have you marked force update records? have you provided adequate user with privileges?
Forced update is set, see image. The DNS properties has secure and non-secure set for DNS updates. Not sure where to find the user privileges settings, but I believe those are set to the system administrator. What would user privileges be for anyway? If DHCP is set up update DNS, what would privileges be needed for?
Jeffrey Kane: > Just create a DHCP reservation for this machine and it will solve your problem.
Yes, this did have the effect of getting the reserved IP into the DNS list! However, it's not exactly what I want. For one thing, I need to set the MAC address to do a DHCP reservation, which means I'll have to remember that if/when I change the network hardware in the DHCP client. Is this just a "bug" in SBS 2008 in that it will only DNS register Windows-only DHCP clients? If so, I guess I'll live with the DHCP reservation solution.
Drashiel: > Have you marked force update records? have you provided adequate user with privileges?
Forced update is set, see image. The DNS properties has secure and non-secure set for DNS updates. Not sure where to find the user privileges settings, but I believe those are set to the system administrator. What would user privileges be for anyway? If DHCP is set up update DNS, what would privileges be needed for?
Jeffrey Kane: > Just create a DHCP reservation for this machine and it will solve your problem.
Yes, this did have the effect of getting the reserved IP into the DNS list! However, it's not exactly what I want. For one thing, I need to set the MAC address to do a DHCP reservation, which means I'll have to remember that if/when I change the network hardware in the DHCP client. Is this just a "bug" in SBS 2008 in that it will only DNS register Windows-only DHCP clients? If so, I guess I'll live with the DHCP reservation solution.
ASKER
Correction: creating the DHCP reservation DOES NOT appear to do the trick. After rebooting the SBS 2008 server (after an update), the DHCP reservation shows in the DHCP manager, but is no longer in the DNS list.
Is this just a "bug" in SBS2008 whereby Microscoft simply doesn't like supporting non-Microsoft systems, or am I doing something fundamentally wrong?
Is this just a "bug" in SBS2008 whereby Microscoft simply doesn't like supporting non-Microsoft systems, or am I doing something fundamentally wrong?
ASKER
OK, I'm going to try this this weekend. I'll have to modify it a bit since I'm using slackware
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry for the delay - this question fell off my radar.
Jeffery Kane, that link seems to have done the trick! The short answer is to put the local/client hostname in the /etc/rc.d/rc.inet1.conf as:
DHCP_HOSTNAME[0]="thishost
Normally I do mention distro and version, but for whatever reason I didn't think this was an issue on the Linux side. The version is question is Slackware distro 13.37.0, kernel 2.6.37.6. Interestingly, I have another host with the most recent version: Slackware distro 14.1, kernel Linux 3.10.17. This one does *not* have the hostname set, but appears to work propertly anyway.
man dhcpcd says, "-h hostname ... If hostname is an empty string then the current system hostname is sent."
Apparently this works correctly for kernel 3.10.17, but not for 2.6.37.6
Jeffery Kane, that link seems to have done the trick! The short answer is to put the local/client hostname in the /etc/rc.d/rc.inet1.conf as:
DHCP_HOSTNAME[0]="thishost
Normally I do mention distro and version, but for whatever reason I didn't think this was an issue on the Linux side. The version is question is Slackware distro 13.37.0, kernel 2.6.37.6. Interestingly, I have another host with the most recent version: Slackware distro 14.1, kernel Linux 3.10.17. This one does *not* have the hostname set, but appears to work propertly anyway.
man dhcpcd says, "-h hostname ... If hostname is an empty string then the current system hostname is sent."
Apparently this works correctly for kernel 3.10.17, but not for 2.6.37.6
ASKER
Thanks! This one's been stumping me for a while!