Changing autodiscover to point to external server dns

I had to change our autodiscover service because the local domain was on the certificate. I've gone through all the steps, uploaded the new cert, and everything is working fine. However, autodiscover still connects to mail.domain.local, instead
of mail.domain.com. Thus, a user leaves the environment, exchange wont connect without a VPN connection. I can not for the life of me figure out how tell autodiscover to use the public mail DNS entry, instead of the local one. I dug down
to find the service connection point record (SCP) is labeled as the "Localserver" Is this what i need to change to make this work right?
Exchange 2010 environment as well.
If the above wasn't clear, when I open outlook and it goes through autodiscover, it populates "server.local" rather than "mail.domain.com".
Thank you!

Can you please post the output of these commands?
Get-clientAccessServer | fl Name,AutoDiscoverServiceInternalUri
Get-OabVirtualDirectory | fl Server,Name,internalurl,externalurl
Get-WebServicesVirtualDirectory | fl name,internalurl,externalurl
And make sure you below ping commands returns your Exchange IP
Ping mail.yourexternalname.com
Ping autodiscover.yourexternalname.com.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.
So as far as the ping goes - I have split DNS setup, and they both point to the internal local IP of the exchange server (when inside our network, obviously). Externally mail.externalname.com will point to the public IP.
Here is the output from the commands - they all look like they should imo and thats why I dont understand why this is still pulling server.local for the server name:
[PS] C:\Windows\system32>Get-clientAccessServer | fl Name,AutoDiscoverServiceInternalUri
Name : LOCALSERVERHOSTNAME
AutoDiscoverServiceInternalUri : https://mail.external.com.com/autodiscover/autodiscover.xml
[PS] C:\Windows\system32>Get-OabVirtualDirectory | fl Server,Name,internalurl,externalurl
Server : LOCALSERVERHOSTNAME
Name : OAB (Default Web Site)
InternalUrl : https://mail.external.com.com/oab
ExternalUrl : https://mail.external.com/OAB
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl name,internalurl,externalurl
Name : EWS (Default Web Site)
InternalUrl : https://mail.external.com/ews/exchange.asmx
ExternalUrl : https://mail.external.com/EWS/Exchange.asmx

Similar Messages

Delete the DNS delegations pointing to this server

Good morning,
I'm getting ready to decommission my Windows Server 2008 R2 server and replace it with a Windows Server 2012 R2 (completely new hardware). After I decommission my current DC I will reboot it, change its IP address and name and then reboot it again.
I am then going to give the new server the old IP and name of my old DC (so basically the name and IP address of the active DC will not change). I'll then promote this server back into the domain. Since the new DC in the end will have the
same IP and NAME as the old DC, should I uncheck the "Delete the DNS delegations pointing to this server" when I decommission the old DC since the new one would have the same name? Thanks!

You can uncheck it and then promote it. Once done, make sure that the new DC is set under
Name Servers tab in your zones properties.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

2 domain, each with 2 way transitive truts, with sub domains pointing to the same DNS server (how should forward and reserver look zone be configured)

Hello,
I found a test environment and I just trying to understand how it works.
If I have two domains (a.com and b.com) with sub domains(a1.com and b1.com) with two way trust and I want them to point to a Windows DNS server. How should the Forward lookup zones and Reverse lookup zones be configured? In forward lookup
zones do I just add a new zone, make them all primary since only one DNS server, add a.com and b.com and do the same for reverse zones.
Do the sub domains need to be added? What about pointers? Do I add the IP address of a.com and b.com in reverse lookup zones.
A side question: When you create a Domain with dns AD intergrated the forward and reserve lookup are automatically created. You don't need to add the zone of the domain you just created but have to add zones of other domains.

Hello,
I found a test environment and I just trying to understand how it works.
If I have two domains (a.com and b.com) with sub domains(a1.com and b1.com) with two way trust and I want them to point to a Windows DNS server. How should the Forward lookup zones and Reverse lookup zones be configured? In forward lookup
zones do I just add a new zone, make them all primary since only one DNS server, add a.com and b.com and do the same for reverse zones.
Do the sub domains need to be added? What about pointers? Do I add the IP address of a.com and b.com in reverse lookup zones.
A side question: When you create a Domain with dns AD intergrated the forward and reserve lookup are automatically created. You don't need to add the zone of the domain you just created but have to add zones of other domains.
Make each domain controller as a DNS server too. Reverse lookup zones & forwarders are not replicated automatically. You can create AD-Integrated reverse lookup zone & set the replication scope.
You can create AD-Integrated DNS zones in the parent/root domain, set the replication scope to the forest-wide & delegate the zones for handling request locally. Once you create AD-Integrated DNS zone & set the replication scope forest wide, all
the zones will appear automatically in each domain's DNS server.
http://awinish.wordpress.com/2011/04/09/configuring-dns-in-child-domain/
Awinish Vishwakarma - MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Subdomian pointing to an external server?

Can a subdomain on a BC site, point to an external server/host?
e.g
mydomain.com (top level domain on Business Catalyst host)
software.mydomain.com (pointing to an external / separate server not on Business Catalyst)
Is this possible?

Sure - we have several such subdomains pointing elsewhere. Just add an A record pointing to the external IP.

I have a local LAN DNS server. My preferences point to that server. Why does dig give me 8.8.8.8 as my DNS server?

I have a local LAN DNS server. My preferences point to that server. Why does dig give me 8.8.8.8 as my DNS server?
Something is/was modifying my DNS preferences to 8.8.8.8 It seems to be pointed correctly now (at my local LAN DNS server), but why was it pointed at 8.8.8.8 before? I never want it pointed to 8.8.8.8

You've hit the nail on the head Ben. For point to point communications, the IP addresses should be fixed, therefore there is no need for DNS. If a DNS is configured, the NIC (Network Interface Card) drivers will try to contact it.
In my test system, I need DNS for the test computer, but I am communicating with a dedicated Spectrum Analyzer over TCP/IP. So I added a second NIC. The main NIC is configured for DNS and all that jazz. The second NIC (plugged into PCI slot) is configured with a hard coded address, no DNS, no Gateway, nothing else. I connect that NIC to the spectrum analyzer using a crossover cable. The analyzer is configured with a hard coded address also. Now my computer can get on our company network, and the spectrum analyzer is isolated from the network, so it can't catch any viruses, etc., and it still talks to the computer. When using a configuration such as this, it is best to use a dedicated address for the 2nd NIC and spectrum analyzer in the range of 192.168.100.0 to 254
- tbob
Inventor of the WORM Global

Point "TargetServerURL" property to External Server

Hi All,
I have 2 servers (Server A,Server B).In "Server B" the SSRS is configured and it is in right condition.And in "Server A" we are building the reports through BIDS which comes with Sql Server.
As we are creating the reports in "Server A" using BIDS and it is holding "TargetServerURL" property in BIDS Solution,So I would like to assign "Report Server" Url of "Server B" to
"TargetServerURL" Parameter property of BIDS solution .
Can any one let me know does this works in storing the reports in "Report Server Database" of Server A
Thanks,
Quality Communication Provides
Quality Work.
Siddiqali Mohammad .

If you change TragetServerURL to Server B, Deployed reports will be stored on
ReportServerDB of Server B.
If you need to store them in ReportServerDB of Server A then point TargetServerURL to Server A.
- Vishal
SqlAndMe.com

OS X Server DNS Best practice?

Hello,
I am having a little trouble with my OS X Server DNS.
I have set up server.example.com and that works fine but now from my internal network I cannot get to:
example.com or
www.example.com
example.com is a website I have set up on a remote webserver.
My records currently look like this.
Primary Zone: example.com
server.example.com - machine
server.example.com - nameserver
Reverse Zone: 50.168.192.in-addr.arpa
192.168.50.25 - reverse mapping
server.portalpie.com - nameserver
My webserver for example.com has an IP of something like 175.117.174.19
How would I get example.com and www.example.com to point to 175.117.174.19?
Thanks

tsumugari wrote:
Hello, DNS for simple name resolution work correctly for internal and external name. Internal it is .lan and external .fr
I think there is perhaps SRV entry to add.
Please do not use .LAN as your top-level domain. That's not a valid top-level domain right now, but it's also not reserved for this sort of use. Either use a real and registered domain, or a subdomain of a real and registered domain, or — if you squat in a domain or try to use a TLD that's not registered — expect to have problems as new top-level domains are added. At the rate that the new TLDs are coming online from ICANN, I'd expect to see .LAN get allocated and used, too.    .GURU, .RIP, .PLUMBING and dozens of other new top-level domains are already online, and probably thousands more are coming online.
SRV records are not related to accessing the Internet, those are service records which some applications use to access certain network services; they're a way to locate a target server and a port for specific applications — CalDAV does use an SRV record, but that's not related to the original posting's issues.   If you're having issues similar to the OP, then access your server and launch Terminal.app from Applications > Utilities and verify local DNS with the (harmless, diagnostic) command-line command:
sudo changeip -checkhostname
Enter your administrative password. That command might show a one-time informational message about the use of sudo, and will usually then show some network configuration information about your server, and then an indication that no problems were found, or some indications of issues. If there are errors reported, your IP network or your local DNS is not configured correctly — I'm here assuming a NAT network.
I usually do this DNS set-up in a couple of steps. First, get private DNS services configured and working. This is always the first step, right after assigning the IP addresses.   It's just too convenient not to have DNS running on your local LAN, once you get to the point of having and running a server.   Then for external access for (for instance) web services, get port-forwarding working at the firewall/NAT/gateway box working; get your public static IP address mapped to the server's internal, private, static IP address. Then get the public DNS configuration to resolve your external domain name to your public static IP address.
My preference is to use separate DNS domains or a domain and a subdomain inside and outside. Using real and registered domains, and not using any domains associated with a dynamic DNS provider — that's possible, but a little more tricky to configure. This internal and external domain usage simplifies certain steps, and it avoids having to deal with cases where — for instance — some of your services have public IP addresses — such as a mail server you might be using — and other services might be entirely private. If you have one domain (or subdomain) be public and one be private, then you don't have to track external IP address changes in your private DNS services; public DNS has just your public stuff, and your private domain (or subdomain) has just your private stuff. Also obviously easy to tell what's inside your firewall, and what's outside, using this.
If you're thinking of running a publicly-accessible mail server, you'll need additional steps in the public DNS.
Little of the above probably makes sense, so here's a write-up on configuring DNS on OS X Server.   All of the Server.app stuff works about the same for general DNS setup, too. More recent Server.app is usually more flexible and capable than the older Server.app stuff, though.

Migrating one email domain to external server

our AD domain "domain1.com" users have @domain1.com, @domain2.com, and @domain3.com (this one is for testing usage) mailboxes/addresses on our internal Exchange 2010 14.01.0438.000 server. All users are on the same domain regardless
of the email address they use. mailboxes with @domain1.com as their primary smtp address are being migrated to an email service outside of our organization/domain but will still remain users on our domain. For those users we'll be creating a new
profile in Outlook pointed at that new external mail server to switch over to on the cutover date while leaving the existing profile as is. Following migration for a period of time we want @domain1.com users to still be able revert to their current
Outlook profile and be able to get to our OWA in case any problems/inconsistencies occurred migrating contents to the new service. It's understood that sending/receiving mail would no longer work for them on the internal Exchange server, the point is just
that they could access the old contacts/calendar/notes/tasks/emails.
My testing with migrating @domain3.com indicated that in order for domain2.com senders to be able to send mail to @domain1.com recipients after the cutover date and have the mail arrive at the external server instead of the internal server, the following
would have to be done:
-domain1.com removed from gatewayproxy attribute in recipient polices -
removal of gatewayProxy via ADSI
-domain1.com removed from exchange >> organization configuration >> hub transport >> accepted domains
-mx record pointing at external mail server added to internal dns server domain1.com zone
-domain1.com removed from smtp proxyAddresses attribute on each mailbox
It seems like there should be a way to achieve the result of getting the mail to the external server without modifying the proxyAddresses attributes so that the users could still get back into the old exchange server after cutover with their original address.
any ideas?
Thanks

the steps to get [email protected] to [email protected] mail sent to external server are clear from testing and additional testing shows some option for still getting into the old mailboxes from clients/owa but not clear is how it could be done while leaving
domain1.com mailbox addresses intact on the old Exchange server and the AD user object 'mail' attribute intact as it was pre-cutover. To expand and rephrase my original post, is there a way to make Exchange determine whether it should route domain1.com
mail internally vs externally via a global setting that would take priority over and cause to be ignored smtp proxyAddresses attributes on individual mailboxes so these don't have to be stripped/modified causing unwanted AD attribute alteration?
objective partially achieved -
AD object for [email protected] mailbox has the following attributes -
proxyAddresses = SMTP:[email protected] (Exchange primary reply-to address) & smtp:[email protected]
'mail' attribute = [email protected]
if we change primary/reply SMTP in exchange to [email protected] and remove SMTP:[email protected], the result of internal mail sent to [email protected] going to the external server is accomplished but the 'mail' attribute in AD then changes to [email protected]
which is unwanted. we still want 'mail' attribute left as is for these users since their email addresses are not changing. access to mailbox contents on old exchange server via old [email protected]'s old outlook profile + OWA still work which
is good though.
also found that adding a domain to organization configuration >> hub transport >> accepted domains as 'external relay' in addition to a send connector for the domain pointed at the MX for the external server still isn't enough to override/ignore
any proxyaddresses on the internal mailboxes. mail willl still end up at the internal mailbox.

Verity K2 Server - point to another server?

Well i am stuck, i have looked through the coldfusion
documentation and also asked adobe support but neither have given
me an answer so far.
I was wondering if anyone out there knows if you can
configure Verity K2 to point to another server in Coldfusion 8
standard edition? The link does not appear in standard but does in
developer/enterprise. If i type the URL in standard i can actually
get to the page that lets you configure another server however when
i save it does not save the change. None of the feature matrix's
out there tell me wether this feature is included in Standard
edition and adobe support dont seem to know either (seriously).
Can anyone out there help me?

Sorry, there are 2 sections that need to be uncommented:


<service id="dnsrv">
<host/>
<load>
<dnsrv>/usr/lib/jabber/dnsrv.so</dnsrv>
</load>
<dnsrv xmlns="jabber:config:dnsrv">
<resend service="xmpp-server.tcp">s2s</resend>
<resend service="jabber.tcp">s2s</resend>
<resend>s2s</resend>
</dnsrv>
</service>

<service id="s2s">
<load>
<dialback>/usr/lib/jabber/dialback.so</dialback>
</load>
<dialback xmlns='jabber:config:dialback'>
<legacy/>
<ip port="7000"/>
<ip port="5269">127.0.0.1</ip>
<ip port="5269"/>
<karma>
<init>50</init>
<max>50</max>
<inc>4</inc>
<dec>1</dec>
<penalty>-5</penalty>
<restore>50</restore>
</karma>
</dialback>
</service>
If you are still having problems, turn off the firewall when you test. If that doesn't work, it is likely a network or dns issue.

Using a site in iWeb to publish to an external server - problems with RSS

Hi!
I have a rather odd problem. I have a .Mac account, but I also work for a non-profit organization that has asked me to handle their website. I would like to use iWeb to do that and am attempting to publish the site to an external server. However, I also want to use iWeb to publish my own personal account pages to .Mac.
I have the site up and running, and most everything works on it except the RSS feed. I typed the url into the Publish to Server dialogue, but it has been to no avail. I wonder if it has to do with the fact that I am not publishing ALL of my sites to this server, just one of the sites. (When I invoke the Publish to Server command, it creates a master index and folders for each of the sites. Then, I have been discarding all of them except for the folder of the site I want to publish, which I have to name "public_html" to conform with our domain provider's requirements. This works great, except the RSS feed is broken when I do this.
I know I can use a seperate log-in account and re-make the entire webpage there, but I consider that to be a last resort and I am looking for a better method than this.
Any suggestions? The site is http://www.oatag.org
Thanks,
Steve
MacBook 2gHz Core Duo Mac OS X (10.4.2) 1 GB RAM, Superdrive, 100 Gig HD

Then, I have been
discarding all of them except for the folder of the
site I want to publish, which I have to name
"public_html" to conform with our domain provider's
requirements. This works great, except the RSS feed
is broken when I do this.
When you break the site structure by changing names of folders you also break the link for the RSS feed.
I find it hard to believe you are really required to change the name of the folder like that. Instead you should be inserting into the folder called public_html the following two things: the folder published by iWeb which has the same name as your site does inside iWeb, plus the index html file published alongside it. To make sure that this index.html file actually points to the site you are uploading, make sure this site is at the top of the list inside iWeb before publishing.

Seeded LOV in OA Page works on internal server, does not in external server

I am using the appraisal creation page '/oracle/apps/per/selfservice/appraisals/webui/MASetupDetailsPG'. Here we have a LOV that lists the appraisal template.
The LOV returns records when Pressing 'Go' from the LOV Search page while accessing from internal server.
However, while performing the same steps from external server, on clicking 'Go' , we get 'No Search Conducted'. ideally , we'll expect the records to come up (or) no results match the chosen criteria. However in this case, it simply gives 'No Search Conducted'.
The 'About this Page' on LOV Page does not show the VO/AM details from external server.
I have checked the following:
1. Class path is same while accessing from both external and internal server
2. Page personalisations are fairly starightforward, just prompts,instruction text changes etc
3. There is no VO/AM customisation. This was done by checking jdr_utils from apps. i suppose this is just application-wide and cannot be checked at server level. pls validate my statement.
4. I have tried 'Diagnostics' using 'About this Page'. It works internally and gives the LOV query with bind parameters. However when I try to do 'Diagnostics'-->Show log on Screen, the screen just hangs before i can see the 'log Level' list on the screen. So I am unable to take trace even from external server.
5. Few other LOVs work from external server. But this one does not.
What could be the cause and how do i debug further?
Any help is appreciated.
Thanks,
LN

As far as I know, if he does what you suggest he won't be able to resolve the "main" domainname.
The internal DNS will think it is the SOA for the "whole" domainname, including subdomain or not, and woun't ask any other DNS. So he needs to add all public IPs/names in his DNS if using the same domainname.
Delegation of a subdomain, this requires both DNS using public IPs:
http://www.zytrax.com/books/dns/ch9/delegate.html
I guess this is "wishful thinking":
IF he (most likely woun't happen) could/be allowed to do zone transfers from a DNS hosting the "main" domainname and run that zone as a slave/secondary on his internal DNS it should work. It wouldn't be ugly if it can be done without adding his internal DNS IP as a NS record. I don't know about notifying the slave about changes to the main domain then though.
If running your own public DNS to separate between public and internal only/private IP lookups depending on what IP the request is coming from:
http://www.zytrax.com/books/dns/ch7/acl.html

Changing AutoDiscover value

Hello!
We have created an Office 2010 MSP installation package using setup /admin. In the Outlook section (Add Accounts), we setup our Exchange server there (let's call it exc2003.company.lan). So when our users opened Outlook, it automatically configured their
email accounts, with no need for them to input anything. That package has been deployed on thousands of machines.
Now, we have decided to change our server to an Exchange 2010 (ie: exc2010.company.lan) so we modified our MSP to point to the new server. For the new installations, they get the new server which is fine.
The problem that we have is for users creating new profiles on machine that have the old installation (and the old server name...), they can't get the automatic configuration because they look for exc2003.company.lan.
Any idea on what I could deploy (GPO?, registry key?), to point the Exchange server to the new one for the installations that have been made with the old setup.
We tought about creating a CNAME entry in the DNS that would make exc2003 point to exc2010 but our network staff doesn't want to do this in case we need to put back the 2003 in service...
Thanks in advance!

Sounds like you deployed a prf-file. Customize the deployment (or Group Policy) to remove that prf-file and additional Registry settings. By default, that custom prf-file is placed in the installation directory of Office.
Robert Sparnaaij
[MVP-Outlook]
Outlook guides and more: HowTo-Outlook.com
Outlook Quick Tips: MSOutlook.info

Has anyone else had problems uploading modifyed files to an external server

Hi, My website bilyz.com has been running OK on two external servers, two different hosting providers, yet neither will allow me to upload modified files.
Since both external servers will run my site OK this narrows the problem source down to my site construction (pre 2014 update) or to Muse software.
The external servers will accept all my html files without a hitch but stalls at various images and not always the same image.
Now I have totally rebuilt the site by stripping out all images, resizing them and remounting them into the slider widget but it doesn't make a difference.
The external server technicians are at a loss to explain and after research have referred me back to Adobe Muse.
Kind regards
Bill Watters

Thank you Aish
As per your suggestion I published the unchanged site to Business Catalyst as bilyzcom.businesscatalyst.com and it uploaded without a fault. Then I made an alteration to the Gallery page where I changed one image in the slider and a small typo on the Design page. Then published again but this time I selected 'options' and clicked on 'modified files only' Result: The site uploaded perfectly and the altered pages showed the recent changes.
So can we conclude that the source of the problem isn't in the Muse software?.
However, If this problem only occurs with the external server since the update; it also stalls when uploading all files and with modified files so could it point to the recent Muse 2014 update?
Yesterday I have also uninstalled my most recent version then re-installed it via the Creative Cloud File manager. . My copy is 2014.0.1.30 CL 785017
I hope this gives you something to work on.
I look forward to your reply.

Mail does not retain correct external server path for Exchange Server '07 even when "automatically detect and maintain account settings" is unchecked. Advice?

Mail keeps resetting the external server path for an Exchange server '07 account when the program is closed and reopened. This happens even though "automatically detect and maintain account settings" is unchecked. To reset to the correct setting I need to disable the account, make the change and save with the account disabled, close Mail, reopen Mail, and enable the account. Then the settings are maintained and Mail works great... until Mail is closed and reopened again. At that point the server path reverts to an incorrect setting. Anyone else experiencing this? Advice? I don't think this is a problem with the Exchange server because this problem did not happen with OS X Mavericks.

This this to fix repeated password requests....
Open Keychain Access in Applications/Utilities
Search for your Dreamhost accounts. There should be two entries (incoming, outgoing) for each account.
It's not uncommon to find old entries. You might want to delete all and start clean.The Keychain isn't smart and will keep all old entries when you add/change a password.
While you are in the Keychain run Keychain First Aid, Under Keychain Access in the Menu bar.
Open Mail
Open Connection Doctor.
If you see red for the account, enter the password again.
If you continue to have problems, delete the account then add it back.

AutoDiscover working Internally and Externally?

What is AutoDiscover and how it works in Exchange 2007 & 2010. Internally and Externally?
Aditya Mediratta

Hi,
Based on my knowledge,in Exchange 2007 and Exchange 2010, Autodiscover is located in CAS server and helps Outlook client automatically find multiple settings including EWS URL and so on.
And there are four connectivity methods for Autodiscover connectivity: SCP,DNS, local XML file and SRV records. Internal Outlook clients will try the four methods while external clients will try the latter three methods.
Except with the above articles, here are more references you can refer to:
http://blogs.technet.com/b/exchdxb/archive/2012/05/10/troublshooting-autodiscover-exchange-2007-2010.aspx
http://support.microsoft.com/kb/2644437
http://support.microsoft.com/kb/2212902
http://support.microsoft.com/kb/2404385
Thanks,
Angela Shi
TechNet Community Support

Changing autodiscover to point to external server dns

Similar Messages

Maybe you are looking for