Hi,
I have a challenge with the following setup:
How do I setup the Z3/ network so that all Z3's connect to the public instead of the corporate IP of the VoIP-Provider?
Thanks in advance!
Are you over thinking this? Can’t you create a new vlan and dhcp pool that assigns a public dns IP address?
@DarrenOC I think @FlyingDutchman wants to use their internal DNS for internal servers, but not for the VoIP server. However they have a DNS entry for the VoIP server on their internal servers that points to a suboptimal IP address.
Therefore the only options I can think of are:
Unless of course I am overthinking this!
@cmr 😆
I think you’re right.
The forth option that @cmr mentioned would work well, this feature is named "DNS views" and is supported in BIND, but sadly not on Windows Server DNS.
So the best long-term solution would be not to use the same domain for internal and external resources. The internal resources should be better migrated to a different domain or a subdomain of company.com.
EDIT: Wait ... just the moment I pressed "Post" I remembered there was a new feature that does exactly what DNS views in BIND are doing, the DNS policies:
https://docs.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-policies-overview
These can be used for this, but are not that easy to configure.
You could configure Windows 10 NRPT - DNS resolution policy.
Configure the policy to send voipserver.company.com to public DNS servers (like 8.8.8.8) and let everything use the default configured DNS servers.