Cloud Service Site Url DNS not resolving

I have a site published to Azure Cloud Services that is running, and accessible via VIP. I cannot access the site via Site Url, even after flushing my local dns, or trying on different devices. In my browser's debugger, I see that DNS resolution
fails in the first step of the web request.
I am relying on the site url for CNAME records - I cannot use the VIP.
What would be causing this? What can I do about it?
Also - if I run whatsmydns.net to query CNAMEs against the cloudapp.net address, I get nothing, but A records are resolving to the VIP.

Hello,
Did your make sure your CNAME is valid? I suggest you could use some DNS tool to query it and check it.
If your dns name is valid, I suggest you could follow tutorial (http://www.windowsazure.com/en-us/develop/net/common-tasks/custom-dns/ ) to step by step.
Please try it.
Any question, please let me know.
Thanks.
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

This database was connected to a Microsoft Access Services site that is not compatible with this version of Microsof Access. You cannot make design changes or modify data in database.

Hello All,
I am getting this error while I am connecting my access database website for the change
"This database was connected to a Microsoft Access Services site that is not compatible with this version of Microsof Access. You cannot make design changes or modify data in database."
I am using SharePoint 2010 and Microsoft Office 2010.
I have created one Contact Database Site and now I am trying to modify the layout of the form in Access. and I am getting the error that I have mentioned.
Please provide help on it.
Thanks in Advance....

Hello All,
I got the answer, we have to enable the port 80 or where the access service is deployed and we have to change Trust setting and also, enable the macro from Access.
Hope this will help to other....

Cloud App Action Service - notification url is not called

Hi
I have created an Eloqua Cloud App with an Action Service.
To test it I created a campaign and added a couple of members but for some reason it seems like the notification url is not called at all.
It set the service up exactly like described here:Develop an AppCloud Action Service
My Notification URL is: http://URL/apps/components/notify?instance={InstanceId}&asset={AssetId}
I had a look in the log file (for the app) and there is no outbound call for the notification url either.
So the question is what am I doing wrong?
thanks,
Simon

Notification is working for us now too, although we are having the same Delete URL problem as Alessandro.
Delete URL has never worked for us (regardless of SP3). I've posed another topic on Topliners about this issue (Delete URL not being called in AppCloud Action Service) and I see that Alessandro has a similar post (App Cloud Delete Url missing call).

DNS not resolving on one Mac but the other works fine in same local network

Snow Leopard is doing something strange to the DNS or the permission to ping.
I have 2 Macs on the same local network, connect through the same ISP (verizon FIOS). One has no problem resolving any domain, but the other is constantly not resolving some domains.
The problem progresses like this:
* All of a sudden, DNS is not resolving from Ethernet (when it did perfectly well a minute ago).
* Then I switched to wireless (using the same LAN), and it resolved fine.
* Then it failed completely a few minutes later.
* Then I reboot my Mac, and it seemed to clear that, and worked for a day.
* Then it failed again in both Ethernet and Wireless; rebooting does not fix it.
* I cleared all the caches using Onyx, did "dscacheutil -flushcache", zapped the PRAM, reinstalled 10.6.2 combo update, repaired the permission, nothing works.
* Since the unresolved domain is my own domain, I changed the nameserver, and waited for it to propagate to see if that may be the problem, since it appeared that it is not resolving the A Record, and I waited 72 hours, and it is not resolved or propagating to the local DNS, but it worked perfectly well on my other Mac within the same network.
* Then I added other DNS, such as google DNS 8.8.8.8 or openDNS servers to it, but it didn't fix anything.
* Then I "ping" either the unresolved domain or my own Mac .local, and it gave me the error "permission denied". (Whereas I have no problem pinging my own Mac or the unresolved domain in my other Mac that works!).
* Then I "sudo ping" the unresolved domain or my own Mac, and it pinged perfectly well.
* Then I tried "ping6" my own Mac or the unresolved domain on the broken Mac, and it worked fine!
* Also, I used http://network-tools.com to ping it, and noticed that during the trace, somewhere along the route through te7-2.dsr02.dllstx3.theplanet.com and po2.car04.dllstx5.theplanet.com, it timed out along the route, so I don't know if the timeout could have been causing the reject, but I doubted, because "sudo ping" locally will get through but "ping" does not.
So I think I traced the Snow Leopard DNS problem as follows:
* Why does "ping6" works, but "ping" permission is denied unless the user is root?
* I tried to "chmod 4755 ping" but it won't let me.
* Is it because DNS is resolving using IPv6 but not IPv4?
* Or is Snow Leopard somehow screwed up the permission to access ping or similar DNS service?
* Why DNS has no problem in one Mac but caused problem on the other Mac, even though they are in the same local network?
* The only difference between the Macs maybe because I have Parallels installed in the Mac that failed to resolve DNS (with the extra Parallels Shared Ethernet), which may be interfering with it, but I tried to turn Parallels Shared Ethernet off, and it did not fix the problem.
Can anyone help or have any idea that I can fix this nagging bug with DNS? The DNS had worked before, but it simply quit working all of a sudden, and nothing can resurrect it.
Thanks.

Shut down Parallels and restart w/o letting any of Parallels TCP/IP stack resurrect itself. So many network issues with VM solutions. See if the problem persists. Create a new account and ping from there. Are your search domains manually entered on the 10.6 box?

Special characters in UCM site URL does not give error

Hey Experts,
If we put any special characters in site URL, UCM does not show 404 page .. for e.g.
site URL is http://www.example.com/abc/xyzs/index.html.... if we add special characters in URL for e.g. http://www.example.com/#$abc/xyzs/index.html...
then home page of site is displayed .....http://www.example.com/...
Also http://www.example.com/ abc/xyzs/index.html shows home page ..
Any idea why it is happening ??

I would attribute this behavious to the SSUrlMap filter - which has the job of turning the friendly URL's into SS_GET_PAGE service calls. Apparently the way it parses the URLs and looks for the patterns does not consider these characters.
Is it actually a problem?
Tim

Deploy Play Framework to Azure Cloud successfully but url is not working

Hi!
Despite the emulator was working nicely, after I've published my play framework app and opened the link, nothing happened. I couldn't even ping the
public virtual IP. My one role instance is running, tried to reboot, no success.
I've followed the tutorial on msopentech (https://msopentech.com/blog/2014/09/25/tutorial-running-play-framework-applications-microsoft-azure-cloud-services-2/).
(Sorry, it says my text cannot contain images or links until they verify my account.)
Could you help me what did I wrong?
My URL is: http://68bf950959ee46a0beb4d8f584a30c04.cloudapp.net
Many thanks,
Csongor

Hi,
The ICMP traffic is blocked by the Azure load balancer and the ping requests timeout.
Note that while this applies to network traffic going through the external IP (VIP) through configured endpoints, ICMP is not blocked when connecting through an Azure virtual network gateway or ExpressRoute. Also, ICMP will work between internal IPs of VMs
in the same virtual network or in the same cloud service.
To test connectivity, we instead recommend that you do a port ping. While Ping.exe uses ICMP, other tools such as PsPing, Nmap, or Telnet allow you to test connectivity to a specific TCP port.
Hope this helps !
Regards,
Sowmya

Application deployed on Oracle Java Cloud Service - SaaS Extension is not connecting with cloud database.

Hello Experts,
I have deployed an ADF application on Oracle Java Cloud Service - SaaS Extension and also deployed database objects from local environment to cloud using JDeveloper. I can see the cloud database has tables and data which I have deployed but when I access the application it seems it is not able to connect with cloud database.
I have followed below document and same sample application (HRSystem).
http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/JDeveloperPart1/jdeveloperPart1.html
http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/JDeveloperPart2/jdeveloperPart2.html
Please guide me what can be the issue.
Regards
Gulam Dyer

Hi,
Can you give us more details about your issue? Any error messages?
Thanks,
Bogdan

Cloud service web role did not get request

Hi Team,
we have an application host in web role in a cloud service,
sometimes it keeps loading when clicking a button in GUI and got no response till our GUI timeout (30 minutes)
we use Fiddler to trace the http request and also check IIS logs and found that sometimes the web role didn't get a request, sometimes the IIS
got the request and finished to processe the request but didn't return result to GUI.
it seems the message lost during interaction between UI and web role.
note that this problems comes out just recently.
is there some known issues related with this kind of problems.
thanks in advance.

hi Baker,
Firstly, I need confirm what's meaning is GUI from your description ? The GUI is your cloud service project UI? Or your UI in your client?
Secondly, base on my experience, we usually could occur timeout error because of the azure load balancer and the long time request.
For this error, I recommend you refer to those thread:
Azure Web Role - Long Running Request (Load Balancer Timeout?)
Windows Azure Load Balancer TimeOut for Cloud Service Roles (PAAS Web/Worker)
Windows Azure Load Balancer Timeout Details
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/89b283f0-dfca-49a7-99fe-c3b73d77ff6d/azure-load-balancer-sending-http-request-to-multiple-web-role-instances?forum=windowsazuredevelopment
If I misunderstood, please let me know.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Airport Extreme 802.11ac local dns not resolving

I have an AirPort Extreme 802.11ac wireless router that I cannot get to resolve local dns names and entries. Everything else is working perfectly, even external dns resolution, but any local dns hostname does not resolve. I can ping the ip addresses of all local systems, I just cannot resolve them. I have checked all configurations and they are set correctly. Please help

adbrennick wrote:
Update:
Setting the AE in Bridge Mode works fine.
Because the dns is then moved to the main router.
Apple are bent on removing as much as possible from even what little was available in 5.6 utility.. so each update removes yet more options.. as for having telnet or ssh .. go wash out your mouth.. they are anathema to Apple total control of the environment.. I mean to say you might set something they didn't intend.

External DNS not resolving SBS2011

Hi,
Hoping someone can help me out here. We have an SBS server that is no longer forwarding external DNS queries. We setup a secondary DNS server onsite so users would still be able to access web resources, but our primary DC only resolve
internal DNS. We have checked the forwarders on the servers (same on both), and one server resolves the forwarders, the other can't.
I have triedrestarting the DNS service, flushing DNS cache and a server restart. I've also checked forwarders and root hints, but can't see anything wrong in the configuration. Both servers have NIC set with the other DNS server as primary and itself
as secondary.
I tried running an nslookup which works when both DNS servers are polled, but fails on the SBS server if it tries to poll itself or an external DNS server.
Anyone have any ideas?
Thanks
Luke

Here is the results from my dcdiag test:
dcdiag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SERVER01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER01
Starting test: Connectivity
......................... SERVER01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER01
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... SERVER01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : domain
Running enterprise tests on : domain.com.au
Starting test: DNS
Test results for domain controllers:
DC: SERVER01.domain.com.au
Domain: domain.com.au
TEST: Forwarders/Root hints (Forw)
Error: All forwarders in the forwarder list are invalid.
Error: Both root hints and forwarders are not configured or
broken. Please make sure at least one of them works.
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 139.130.4.4 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 139.130.4.4
DNS server: 139.134.5.51 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 139.134.5.51
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.41.0.10 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.10
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
DNS server: 203.50.2.71 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 203.50.2.71
DNS server: 203.8.183.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 203.8.183.1
DNS server: 208.67.220.220 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 208.67.220.220
DNS server: 208.67.222.222 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 208.67.222.222
DNS server: 209.244.0.3 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.3
DNS server: 209.244.0.4 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.4
DNS server: 210.23.129.34 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 210.23.129.34
DNS server: 220.233.0.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 220.233.0.1
DNS server: 220.233.0.2 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 220.233.0.2
DNS server: 4.2.2.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 4.2.2.1
DNS server: 4.2.2.2 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 4.2.2.2
DNS server: 61.8.0.113 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 61.8.0.113
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: domain.com.au
SERVER01 PASS PASS FAIL PASS PASS PASS n/a
......................... domain.com.au failed test DNS
Hope this helps.
Thanks
Luke

New Cisco Linksys e4200 internal DNS not resolving

I have a e4200 sitting behind a BT home hub 2. The home hub provides internet connection to the e4200, and the e4200 allows all devices to connect. I am able to ping internal IP addresses, but when I try to ping by device name it returns the external IP address. How can I view / amend the DNS table on the router?

I've amended entries to protect my security, but this should give the general gist:
Windows IP Configuration
   Host Name . . . . . . . . . . . . : E001
   Primary Dns Suffix . . . . . . . : MyHome.net
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : MyHome.net
                                       home
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connection
   Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.65(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 17 January 2012 18:24:56
   Lease Expires . . . . . . . . . . : 17 January 2012 20:03:56
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.1.254
                                       192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.home:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
The "external IP address" which it resolves to is 82.98.86.161 www161.sedoparking.com - thank you for asking, I was previously assuming (incorrectly) that it was resolving back to the external IP address assigned by my ISP.
I'm still none the wiser as to why names are not being resolved at the linksys router for the internal network.

DNS not resolving on local network

When I initally set up the server I could go to ktecserver.ktec.us and it would resolve and let me access the server, now the only way to do it is to use ktecserver.local (which sometimes works) but mostly I am stuck with using the IP address of the server to get to it. I have the server as the default dns server for the client computers but it doesn't seem to work. I don't know what has changed or where I need to look to try and troubleshoot this.
Also I want to set it up so people can go to something like x.ktec.us and get to specific services on my mac. One thing I don't know about is security, I'm very hesitent to expose any of my server to the internet because I don't know how to properly log/defend against attacks and intrusions, any advice would be great.
Thanks
Message was edited by: TimThor

You want LAN DNS working, then you want public DNS working.
I'm using an airport extreme as a router (so I guess NAT firewall ;P ) and the VPN service on the server.
I am well aware of what you are running, of your configuration goals and current set-up, with the various issues and discussions around VPN pass-through (in general and with the Apple devices specifically, and often around L2TP pass-through), and that this configuration is a frequent topic of discussions here in the forums.
Having a VPN-capable firewall makes for a simpler configuration, and also allows you to access various (other) hosts on your LAN when your server is down.
Which logs should I be looking at?
It's usually dig and ping commands to determine what's working and not working with DNS, and not logs. Typical commands include...
$ dig host.example.com
$ dig -x host.ip.address.here
$ ping host.example.com
$ traceroute host.example.com
You're looking to determine if the forward and reverse DNS translations work, and if they match, and if you can ping the host, and then (potentially) what the IP route to the host might be.
Also why would it just quit working, I can verify that the airport extreme is giving out the right DNS server
The address of that DNS server would be the IP address of the DNS server on your LAN, and no ISP DNS servers, correct?
With remote access via VPN, you need have IP routing correct, and this means that both ends of the VPN need to be in different subnets, and it's typical to have issues when the target LAN is in 192.168.0.0/24 or 192.168.0.0/24, and it's common to move NAT'd LANs that you manage out of 192.168.0.0/16 and into a subnet somewhere in the 172.16.0.0/12 or 10.0.0.0/8 blocks.
You can also try forcing all traffic onto the VPN as a test. That's an option on the VPN set-up.

Any solutions to the DNS not resolving IPv6 problem?

Hello,
Does anyone know how to fix the broken DNS behaviour that was introduced into OS X sometime since 10.4? I'd like to have my systems be able to resolve AAAA addresses, but Apple seems to have broken DNS resolution (probably in response to people complaining about problems which are a result of other IPv6 equipment which are broken!)
Note that this has nothing to do with whether IPv6 works. It does. It's just that OS X's DNS resolver does not return AAAA records at all. Take a look:
[lain:~] john% ping6 andromeda.ziaspace.com
ping6: No address associated with nodename
[lain:~] john% host -t aaaa andromeda.ziaspace.com
andromeda.ziaspace.com has AAAA address 2001:4830:1200:17::2
[lain:~] john% ping6 2001:4830:1200:17::2
PING6(56=4088 bytes) 2001:4830:1700:18::2 --> 2001:4830:1200:17::2
It'd be nice if Apple had a technote or a preference somewhere...
Mac mini Mac OS X (10.4.6)
Mac mini Mac OS X (10.4.6)

If i recall the message is about DirectPlay?
When i installed and ran pse 12 on windows 8.1, windows offered to turn that on.
You might have to go to the Control Panel>Programs>Programs and Features>Turn Windows Features on or off>Legacy Componets>DirectPlay

Site Url is not properly formed in Powershell?

Hi,
I've been trying to add files to a site on SharePoint Online via PowerShell
$SiteUrl = Get-SPOSite https://company.sharepoint.com/site1
However, every time i run the script i get this error:
Get-SPOSite : The site https://company.sharepoint.com/site1 is not properly formed.
I have connected to sharepoint with the Connect-SPOService command correctly.
What is wrong with the url?
Thanks
Dearbhla
Dearbhla Bradley

$SiteUrl = Get-SPOSite -Identity https://company.sharepoint.com/site1

DNS not resolving to new machines on network after increasing DHCP pool size

Hello,
I am having a very strange issue with connecting new machines to reach the internet.
We have a ASA 5505 which the previous tech configured the DHCP pool to 192.168.1.60 - 192.168.1.110
We ended up reaching our limit which I changed it to: 192.168.1.60 - 192.168.187
Then next day when I arrived to work, our DC was hung from windows updates. Once we got everything back up, every computer currently on the network can reach the internet/VPN tunnels etc. So (continuing with my day) I created a new server in a VM (Hyper-V)
I can ping everything internally (even the router) 192.168.1.1, but I cannot resolve DNS. I have configured a static IP, tried Dynamic IP.
I have looked for any ACL indicating to block outside the range of the old DHCP pool but no luck.
On my local maching I can ping the DNS addresses, but just not on the new server.
Can anyone point me in the right direction to where to look for this issue?

I ended up figuring out what the issue was.
Since it was in a Hyper-V VM. the hosting server had to be updated to SP1.
Once completed, and rebooted. The VM in question got an IP address.

Cloud Service Site Url DNS not resolving

Similar Messages

Maybe you are looking for