<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problems caused by Splunk web interface url in Security</title>
    <link>https://community.splunk.com/t5/Security/Problems-caused-by-Splunk-web-interface-url/m-p/69526#M2269</link>
    <description>&lt;P&gt;I'm installing Splunk 4.3 on EC2 instance(Linux image) and want to access the Splunk web interface outside of EC2. The problem is every EC2 instance have two DNS, one is privete DNS and the other is public DNS. For example, &lt;BR /&gt;
Public DNS:ec2-75-101-214-21.compute-1.amazonaws.com, &lt;BR /&gt;
private DNS:ip-10-80-201-152.ec2.internal&lt;BR /&gt;
After I start splunk, it says: The Splunk web interface is at &lt;A href="http://ip-10-80-201-152:8000"&gt;http://ip-10-80-201-152:8000&lt;/A&gt;. Actually, this is neither public DNS nor private DNS. It is just a part of the private DNS!&lt;BR /&gt;
How can get around this problem? Can I change the Splunk web interface url(DNS)?&lt;/P&gt;</description>
    <pubDate>Fri, 10 Feb 2012 10:55:43 GMT</pubDate>
    <dc:creator>liny</dc:creator>
    <dc:date>2012-02-10T10:55:43Z</dc:date>
    <item>
      <title>Problems caused by Splunk web interface url</title>
      <link>https://community.splunk.com/t5/Security/Problems-caused-by-Splunk-web-interface-url/m-p/69526#M2269</link>
      <description>&lt;P&gt;I'm installing Splunk 4.3 on EC2 instance(Linux image) and want to access the Splunk web interface outside of EC2. The problem is every EC2 instance have two DNS, one is privete DNS and the other is public DNS. For example, &lt;BR /&gt;
Public DNS:ec2-75-101-214-21.compute-1.amazonaws.com, &lt;BR /&gt;
private DNS:ip-10-80-201-152.ec2.internal&lt;BR /&gt;
After I start splunk, it says: The Splunk web interface is at &lt;A href="http://ip-10-80-201-152:8000"&gt;http://ip-10-80-201-152:8000&lt;/A&gt;. Actually, this is neither public DNS nor private DNS. It is just a part of the private DNS!&lt;BR /&gt;
How can get around this problem? Can I change the Splunk web interface url(DNS)?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2012 10:55:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Problems-caused-by-Splunk-web-interface-url/m-p/69526#M2269</guid>
      <dc:creator>liny</dc:creator>
      <dc:date>2012-02-10T10:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Problems caused by Splunk web interface url</title>
      <link>https://community.splunk.com/t5/Security/Problems-caused-by-Splunk-web-interface-url/m-p/69527#M2270</link>
      <description>&lt;P&gt;Splunk attempts to determine the URL - but it doesn't enforce it anywhere.   It is simply listening on port 8000 on your server.&lt;/P&gt;

&lt;P&gt;You should be able to access it at &lt;A href="http://your.public.address:8000"&gt;http://your.public.address:8000&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2012 12:55:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Problems-caused-by-Splunk-web-interface-url/m-p/69527#M2270</guid>
      <dc:creator>Linegod</dc:creator>
      <dc:date>2012-02-10T12:55:57Z</dc:date>
    </item>
  </channel>
</rss>

