Comments

  • I get that it isn't a DNS server and just a forwarder. I haven't had a chance to try and dig into the inter-VPN links, but it does appear to at least forward the registration requests locally. That is pretty good. It would be even nicer it it would allow for that to be done in a secure manner, but in this case it isn't…
  • yea... not using DNSWatch, just trying to use the firebox as the primary DNS server and take advantage of DNS forwarding for the internal domains. The biggest driver is for the remote sites since it doesn't make sense to send the DNS query back through the VPN for things like google.com. I think dynamic DNS registration is…
  • @Bruce_Briggs - that is exactly what I'm trying to use, but as I said, it appears that my choice is that if I use it, I lose client DNS name updates for our internal DNS servers. @GreggHill - I"m going to retry now with my guest network which updates quickly to see if my recent changes pass those names back to the internal…
  • James, if someone is on server 2012, they are either out of support with Microsoft and not doing updates OR they are paying significant money to Microsoft for extended support to continue updates. Either way, they wouldn't be holding onto a windows 2012 hyper-v host. Maybe a physical 2012 server is needed or a 2012 VM is…
  • James, Continued support for Server 2012 is a rather funny reason. Microsoft stopped mainstream support for Server 2012 over 6 months ago! I"m pretty sure its safe to say any company still running a windows 2012 hyper-v host is also unlikely to upgrade their dimension server. For an IO and network intensive VM, Its a shame…