This option is normally not required by the Mac OS X DNS search system when the resolver configuration is read from a file in the /etc/resolver directory. It did work as expected, but I wasn’t sure what’s happening.ĭomain name associated with this resolver configuration. I saw this article Use different DNS servers for different domains and gave it a try. So I started to search whether there are better solutions. A former colleague even gave a confused look after he heard this. Periodically resolve internal websites (using CronJob) that I frequently use with internal DNS server, write to /etc/hosts, then set my system-wide DNS server to external ones. dev ones.Īt first, I decided to use a bizarre way to solve this problem by: If I use external DNS servers like the Google ones, I won’t be able to resolve internal websites, and that’s not just.If I use corp’s DNS server, I won’t be able to visit these.It seems I didn’t have a perfect solution: There were lots of internal websites that won’t be able to resolve now. I tried to bypass this by changing my DNS server to Google Public DNS, but other problems were starting to show up. I asked some colleagues, and that’s when I learned that the corporation’s DNS server did something on. However, after I encountered this situation several times, it became somehow frustrating. It was inconvenient, but I didn’t overthink it at that time. dev domains when using the corporation’s network. A few months ago, I noticed that I couldn’t visit to any.
0 Comments
Leave a Reply. |