Workaround for missing RFC 2136 feature
-
Hi everybody,
I've a problem with the DNS registrations of my Snom phones. I hope somebody could help me out with a workaround.
There is one HQ with Windows Server as DHCP, DNS, AD and many remote sites with pfSense as router, DHCP, DNS. On all sites there are Snom phones which get an IP from the local DHCP and therefore are registered on the DNS (with their extension as hostname).
Now we need those DNS records in our Windows DNS server. How could I manage that? All sites are connected via VPN. I thought of pointing all Snom phones to the Windows DNS, so they register themselfs via RFC 2136, but this feature seems to be missing on the Snom devices.
Unfortunately all pfSenses and the Windows server are hosting the same DNS zone, otherwise I could have delegated the queries to the pfSense DNS servers, right?
greetings,
Karsten -
Okay. I'll reply to myself: it was super easy:
https://japtaincack.blogspot.com/2018/02/pfsense-dhcp-dynamic-dns-updates-to.html
But I think I found a bug in pfSense, because I configured this for the DHCP on only ONE specific interface, but now it registers ALL clients from all LAN subnets in the remote DNS. Do somebody know how to prevent this?
I also don't know why it creates a TXT record for every client, would also be nice not to have this.