<?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>question Re: Renaming the instance url in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/renaming-the-instance-url/m-p/3423761#M5367</link>
    <description>&lt;P&gt;It's better&amp;nbsp;not to rename the instance. Rename the URL you expose instead.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Keep the native URL (&lt;EM&gt;https://&amp;lt;instance&amp;gt;.service-now.com&lt;/EM&gt;) as-is. Renaming the &lt;EM&gt;instance name&lt;/EM&gt; is generally not supported/recommended and can break upgrades, support tooling, and vendor-side automation.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Use vanity (custom) DNS names per environment and make those the only URLs end-users and integrations see, e.g.:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;EM&gt;itsm.dev.company.com, itsm.test.company.com, itsm.company.com &lt;/EM&gt;(prod)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Mon, 10 Nov 2025 20:37:28 GMT</pubDate>
    <dc:creator>Sreeram Nair</dc:creator>
    <dc:date>2025-11-10T20:37:28Z</dc:date>
    <item>
      <title>Renaming the instance url</title>
      <link>https://www.servicenow.com/community/community-central-forum/renaming-the-instance-url/m-p/3423748#M5366</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;In our environment, the naming of the sub productions are done incorrectly at the implementation time.&lt;/P&gt;&lt;P&gt;Renaming the url/instance -&amp;gt; is this&amp;nbsp; recommended ? complexity level?&amp;nbsp;&lt;/P&gt;&lt;P&gt;what is the best practice?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2025 20:14:21 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/renaming-the-instance-url/m-p/3423748#M5366</guid>
      <dc:creator>MThomas1</dc:creator>
      <dc:date>2025-11-10T20:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Renaming the instance url</title>
      <link>https://www.servicenow.com/community/community-central-forum/renaming-the-instance-url/m-p/3423761#M5367</link>
      <description>&lt;P&gt;It's better&amp;nbsp;not to rename the instance. Rename the URL you expose instead.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Keep the native URL (&lt;EM&gt;https://&amp;lt;instance&amp;gt;.service-now.com&lt;/EM&gt;) as-is. Renaming the &lt;EM&gt;instance name&lt;/EM&gt; is generally not supported/recommended and can break upgrades, support tooling, and vendor-side automation.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Use vanity (custom) DNS names per environment and make those the only URLs end-users and integrations see, e.g.:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;EM&gt;itsm.dev.company.com, itsm.test.company.com, itsm.company.com &lt;/EM&gt;(prod)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 10 Nov 2025 20:37:28 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/renaming-the-instance-url/m-p/3423761#M5367</guid>
      <dc:creator>Sreeram Nair</dc:creator>
      <dc:date>2025-11-10T20:37:28Z</dc:date>
    </item>
  </channel>
</rss>

