Re: FreeBSD workstation in a Windows Active Directory network: DDNS update?

From: MattD.. (mattd145_at_gmail.com)
Date: 10/08/04 

Date: Fri, 08 Oct 2004 09:05:46 +0100

On Friday 08 Oct 2004 06:38, the whim of a few quarks and leptons to be
Andrew Reilly for a while caused the following to be typed:

> I've tried this with the server-update part both "on" and "off".  On
> doesn't seem to produce any spurious warning messages, but neither does it
> get this machine's name into the AD DNS.  "Off" at least shows some
> activity, producing a series of log messages like:
>
> Oct  8 15:02:05 ghanamia dhclient: Unable to add forward map from
> ghanamia.lake. to 192.168.10.140: timed out
>
> So presumably there's still some magic that I'm not fully tweaking.

This usually implies there is a static record already in place with BIND,
where an nsupdate remove on the fqdn fixes this. Quite how one would go
about this on an MS DNS server I don't know. You may also like to lower
your lease times in DHCP, which in turn should expire stale DNS records
before they bite you.

Either that, or the DNS server isn't allowing updates from the 192.168.10/24
subnet for non-Windows clients. I'm assuming that the DNS is on the AD
controller and the Windows clients are all NT based members of the domain,
in which case they'll be authenticating on getting a lease (you can set the
zone to allow updates from authenticated clients or "anybody" in the
security profile of the AD controller, but this is very insecure). You may
need to open up the zone to allow updates from unknown clients.

If you don't get anywhere, let me know and I'll dig out King's "Mastering
AD" and try to give you a few more ideas. 

-- 
Radio glossary #23
Mast: A device guaranteed to cause TVI even when surmounted by nothing
more than a white painted broom handle.

Relevant Pages

  • Re: Vista clients became unresponsive after network move
    ... being used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... 11/5 - DNS server has started ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... If DHCP is not being used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... DNS server events since the move: ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... If DHCP is not being used, and all clients are static and incorrectly configured, I can understand the problems. ... network connection. ... reverse zone. ... 11/5 - DNS server has started ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... DNS server events since the move: ...
    (microsoft.public.windows.server.networking)
  • Re: DNS server not populating zone file
    ... I will look into changing our setup to only allow clients to register. ... pushed from the DHCP server whenever the lease expires (or I do ipconfig ... Yes you will need to allow insecure updates if you ... An easy way to move zone data from one DNS server to another (no matter ...
    (microsoft.public.windows.server.dns)
Loading