Hey everyone! I'm currently working on implementing a VPN solution that includes internal gateways and host detection. We've been running into some issues, and it seems like a lot of them are linked to DNS resolution and the split-tunnel logic. What's worrying is that the architect from the vendor who's supposed to be guiding us said, 'DNS isn't really my strong suit.' This raised some major red flags since DNS is going to be a crucial aspect for multiple projects we have going on. I understand not everyone can know everything, but shouldn't understanding DNS be essential when designing enterprise network access, especially for VPNs? I'm curious about your thoughts on a few things: Should I push back or escalate since the vendor architect lacks DNS expertise? How can I raise this concern tactfully without damaging our relationship with the vendor? Or should I just factor in more testing and validation to accommodate their shortcomings? I'm aiming to prevent a 'we'll fix it later' scenario that leads to chaos down the line.
3 Answers
Honestly, it's not on you to sugarcoat it. You need to be straightforward with the architect about your concerns. If they're not willing to learn or justify their DNS strategies, then you might need to consider finding someone else. It’s about your project’s success, after all!
Honestly, DNS has always been crucial! You should definitely make sure that your architecture considers this from the start. If you're unsure, raise questions with the vendor and ensure you have a solid understanding before moving forward. It’s better to get it right at the design phase than later on!
Absolutely, I’m on it! Thanks for your input.
Just a heads-up! In network engineering, knowing your DNS inside and out is critical. Don’t hesitate to ask for detailed architecture plans and diagrams regarding their DNS setup. If something doesn't sit right with you, don't be afraid to address it with the vendor.
Thanks for the tip, I appreciate it!
This advice really puts things into perspective, thanks!