<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Dns on Holyarmy.org</title>
		<link>https://holyarmy.org/tags/dns/</link>
		<description>Recent content in Dns on Holyarmy.org</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 23 Jul 2008 18:20:19 +0000</lastBuildDate>
		
			<atom:link href="https://holyarmy.org/tags/dns/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Fight Back! (When VPN Clients Mis-Behave)</title>
				<link>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</link>
				<pubDate>Wed, 23 Jul 2008 18:20:19 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</guid>
				<description>&lt;p&gt;I have to use VPNs at work. Specifically, to access my production webservers (etc), I have to use a Cisco VPN client. Sadly, the VPN concentrator overrides my choice of allowing local LAN access. So, when I am on the VPN, I have my DNS options changed so I can’t use any local servers. This is a serious, serious pain. So painful in fact, that many times instead of fight with it, I simply would run a Windows session in VMware (on my Mac) and connect the VPN there. This has drawbacks too, but it’s better than not having local network access.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Network Directory Services</title>
				<link>https://holyarmy.org/2007/10/network-directory-services/</link>
				<pubDate>Sat, 06 Oct 2007 21:00:41 +0000</pubDate>
				<guid>https://holyarmy.org/2007/10/network-directory-services/</guid>
				<description>&lt;p&gt;Network directory services are core to Internet functionality. The &lt;a href=&#34;http://en.wikipedia.org/wiki/Domain_Name_System&#34;&gt;Domain Name System (DNS)&lt;/a&gt; provides a global (and/or local) directory of hosts and services. &lt;a href=&#34;http://en.wikipedia.org/wiki/LDAP&#34;&gt;Lightweight Directory Access Protocol (LDAP)&lt;/a&gt; servers can provide some of the same information as DNS (or be used to back DNS), but are more frequently used to create network user databases, store user group information, providing centralized account information and password storage.&lt;/p&gt;&#xA;&lt;p&gt;I recently completed an upgrade of these two core services on a network I manage. We had been running outdated (but functional) &lt;a href=&#34;http://en.wikipedia.org/wiki/BIND&#34;&gt;BIND&lt;/a&gt; v8 and &lt;a href=&#34;http://en.wikipedia.org/wiki/Openldap&#34;&gt;OpenLDAP&lt;/a&gt; v2.0 instances for of DNS and LDAP servers. Also, throw a Windows Server 2003 into the mix, which, as an &lt;a href=&#34;http://en.wikipedia.org/wiki/Active_directory&#34;&gt;Active Directory&lt;/a&gt; domain controller has to run its own DNS and LDAP (AD is tweaked LDAP) servers.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
