<?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 Re: trouble in web server in Server Networking</title>
    <link>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/5302353#M13854</link>
    <description>&lt;P&gt;hmm am not sure but is the DNS set up correctly for internal domains like that? sometimes our team had issues with .corp URLs not resolving unless the DNS server knew about them. also just to confirm, are you testing this inside the company network or from outside?&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jun 2025 11:32:30 GMT</pubDate>
    <dc:creator>Chloeharper</dc:creator>
    <dc:date>2025-06-25T11:32:30Z</dc:date>
    <item>
      <title>trouble in web server</title>
      <link>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/4890676#M13659</link>
      <description>&lt;P&gt;hello everyone, I have a problem at Cisco when I want to enter the url address &lt;A href="http://www.cisco.corp" target="_blank"&gt;www.cisco.corp&lt;/A&gt; on the web server. immediately occurred Host Name Unresolved how to overcome it how yes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 04:00:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/4890676#M13659</guid>
      <dc:creator>Robbybaehaqi8</dc:creator>
      <dc:date>2023-07-24T04:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: trouble in web server</title>
      <link>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/4890733#M13660</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1559986"&gt;@Robbybaehaqi8&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Do on the server &amp;gt;nslookup&amp;nbsp;&lt;A href="http://www.cisco.corp" target="_blank"&gt;www.cisco.corp&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Does an IP is returned ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 04:38:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/4890733#M13660</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2023-07-24T04:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: trouble in web server</title>
      <link>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/5302353#M13854</link>
      <description>&lt;P&gt;hmm am not sure but is the DNS set up correctly for internal domains like that? sometimes our team had issues with .corp URLs not resolving unless the DNS server knew about them. also just to confirm, are you testing this inside the company network or from outside?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2025 11:32:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/5302353#M13854</guid>
      <dc:creator>Chloeharper</dc:creator>
      <dc:date>2025-06-25T11:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: trouble in web server</title>
      <link>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/5303173#M13855</link>
      <description>&lt;P&gt;what does &lt;A href="http://www.cisco.com" target="_blank"&gt;www.cisco.com&lt;/A&gt;&amp;nbsp;return?&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.corp" target="_blank"&gt;www.cisco.corp&lt;/A&gt;&amp;nbsp;is not an active, and I don't think .corp domain names are valid overall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kirk...&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jun 2025 18:51:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/server-networking/trouble-in-web-server/m-p/5303173#M13855</guid>
      <dc:creator>Kirk J</dc:creator>
      <dc:date>2025-06-26T18:51:03Z</dc:date>
    </item>
  </channel>
</rss>

