<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Remote Access Design Guidelines – Part 4: IP Routing and DNS</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-4-ip-routing-and-dns.aspx</link><description>Hello Customers, In this post, I will walk through some aspects on IP addressing, routing and name resolution related design guidelines. 4. 1 IP Addressing The VPN client machine will have minimum two IP addresses – one that it gets from ISP through which</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Remote Access Design Guidelines – Part 1: Overview and References</title><link>http://blogs.technet.com/b/rrasblog/archive/2009/03/17/remote-access-design-guidelines-part-4-ip-routing-and-dns.aspx#3213945</link><pubDate>Tue, 17 Mar 2009 14:53:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3213945</guid><dc:creator>Routing and Remote Access Blog</dc:creator><description>&lt;p&gt;Hello Customers, In last few releases, we have added plenty of “cool” features in RAS – like NAP based&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3213945" width="1" height="1"&gt;</description></item></channel></rss>