Hello All Netwoking Guru!
I purchase Mikrotik RouterBOARD 1100AH and got a configuration trouble with updating PTR records in reverse zone of Microsoft DNS. I have a domain an DNS server on domain controller, also have a configured dhcp server on the Mikrotik router. Reverse zone on dns 5.168.192.in-addr.arpa configured for receiving non secure updates. But Router can’t update this zone, it’s empty all time. Primary A zone updated successfully every time as client gets a new address. I run a Network Monitor on the DNS server and can’t see PTR update requests. When I set a static ipv4 address and run on client “ipconfig /registerdns”- all ok. Where is my error?
p.s. I also trying to config a DHCP Relay on another dhcp in my domain, all works too, but I want dhcp on router ))
I don’t believe you can configure MT’s DHCP server to send PTR updates to another DNS server.
The reason the /registerdns command works fine is because the CLIENT is doing the leg work - it contacts your AD servers and initiates the update.
Your only resolution is to use an AD DNS server if you want your PTR domain updated. Otherwise you might have to run some type of scheduled script on all of your computers to have them manually register their DNS entries.
Your only resolution is to use an AD DNS server if you want your PTR domain updated.
Thank you for reply!
I’m already use AD DNS servers (natively from Windows server). When I’m setting MK router as dhcp relay and point it to MS dhcp, all works good. When I configure router as standalone dhcp server - primary zone updating, reverse zone still not. I heard MS Server have special policy setting for its PTR records, but can’t find it. May be it only rumors ))
Sorry, I mistyped - I meant to state AD DHCP server. I’m not sure on the particulars of how MS has things set up internally, but I usually like to keep it simple and just let their tools do the leg work with their system. As you stated, you can do DHCP-relay to another DHCP server and get your PTR records updated that way. Otherwise your only other recourse is to run the /registerdns command on the client so that it initiates the update for you.