(I'm new to zones and AAMs so apologies if this question comes across a bit incoherent... I haven't really grasped how it all works yet.)
I have a Publishing site in SharePoint, running in a web app configured to use port 4444. When it was initially created it was only configured with the Default zone, which was using an internal URL only recognisable by the SharePoint server the web app is running on. (say http://localhost:4444)
Subsequently, to make the Publishing site publicly viewable, we set up a public URL to access the server. (say http://publicurl.com:4444). It seemed OK at first but then I realised that some URLs were still pointing to the internal server address, which obviously couldn't be resolved when accessing the site publicly. So I extended the web application to a new IIS web site on port 6666, and set this as the Internet zone.
So now we can access the site via http://publicurl.com:6666, and this seems to have solved the problem of the incorrect internal URLs. But I'm uncertain as to whether this extended web application, on the new zone, fully mirrors the original web app on the default zone. For example, I am using the MossMenu component with the CSS Friendly Adapters for my navigation. However I had to re-add the MossMenu to the SafeControls for the new web app (6666) in its web.config. And as of yet I still haven't got the CSS Friendly Adapters working for the new app/Internet zone, even though they work when using the Default zone and the internal URL.
So I guess my question is... does the extended web app/new zone fully mirror the original app/original zone, or are there usually a bunch of things I need to manually mirror? For example, say I deploy a new web part, would I need to deploy it to both the original web app and the extended web app?