DNS record update over DHCP server

Hi all!

I’ve read lots of stuff (Mikrtoik forums also) regarding updating DNS records in Microsoft DNS server over different DHCP servers. I’m sorry to say i’m lost. I’m at the point where i think i’ve read and tried everything.


Description:

Our company has many branch offices connected to main location (over VPN, wireless). There is a primary domain controller (pdc - win2003server) with DNS server ofcourse. Every branch office has it’s ovn Mikrotik router, with RIPv2 support, and of course main location too.

Problems:

  1. When i try to connect through a computer using PPTP conncetion (DHCP distributes addresses) I get connected, everything works fine except that computer doesn’t update its DNS record on the PDC. The computer is a member of domain and gets its record updated when connected directly through LAN, WLAN.

  2. Computer is not a member of a domain and is connected through LAN. Its record doesn’t get updated in PDC

Tried:

    • typing ipconfig/dnsregister after connecting works and computer is registered! - WORKS
  • tried putting DHCP option 015 with domain.com on MT DHCP server or domain.com under dns domain in DHCP server options - DOESN’T WORK
  • tried manually adding dns suffix and registration in windows cliend IP config - WORKS!


    I have a domain.com forward zone set in PDC. Dynamic updates set to secure and non-secure.

I need to get random network devices (that are not necesserily on a domain) to get registered to Microsoft DNS using Mikrtoik DHCP server. Any clues?

P.S.

domain.com = internal domain

Set the primary DNS address to the AD DNS server. Windows clients dont update through DHCP these days (Never did actually, the DHCP server itself was what did the updating), they update via DNS.

Primary DNS is set to PDC.
Secondary DNS is set to Secondary DC.

Primary DNS on PDC shows on secondary DC and vice versa.

Then it should work. If the clients primary DNS as assigned by the routerboard is the AD DNS server, the DNS should be updated. The subnet would need to exist in DNS, of course. If the client is using MT as its DNS server and MT forwards requests to the AD DNS server, it wont work.

The main problem i can’t seem to solve is that computers that are not on the domain can’t update the dns records on PDC.

They wont be able to unless the domain DHCP server gives the address.. They update DNS with the computer account credentials, which non-domain computers dont have.

Bummer :frowning: . Tnx for effort and info.