It takes 9 seconds for a my domain oratorius.com to be resolved, if I use the nslookup command I have to set the timeout to 9 seconds, otherwise I get a timeout. Users have problems getting to my site. My domain host'er says:
The delay is not occurring on our end, you have CNAME records directed to
oratorius.cloudapp.net which is where the delays seem to be coming from. You
need to contact the DNS administrators for this hostname to find out what
the problem us.
Are anyone else having the same issue with Azure? How should I start troubleshooting?
Here is some proof:
C:\Windows\system32>nslookup oratorius.com
Server: ad3.example.no
Address: 10.1.1.10
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Request to ad3.example.no timed-out
C:\Windows\system32>nslookup
> set timeout=9
> oratorius.com
Server: ad3.example.no
Address: 10.1.1.10
Non-authoritative answer:
Name: oratorius.cloudapp.net
Address: 65.52.66.8
Aliases: oratorius.com
But you can't have a CNAME record for oratorius.com (CNAME records can only exist for subdomains, like www.oratorius.com), right?
You should be able to directly check the DNS resolution time on oratorius.cloudapp.net, right? When I ping www.oratorius.com or oratorius.cloudapp.net, both seem to resolve at about the same speed.
(I can't get nslookup to look anything up...)
See http://dnsazure.com, this is a paid service for naked domains on Windows Azure.
Related
I have a strange DNS error when attempting to access the domain rrrr.com. I have called to my ISP technical support, but they said they would call back and have not.
The domain is not accessible, but all the records and servers are correct.
nslookup rrrrr.com 167.206.10.179
Server: 167.206.10.179
Address: 167.206.10.179#53
** server can't find rrrrr.com: SERVFAIL
Where 167.206.10.178 and 167.206.10.179 are my ISP DNS servers.
Using OpenDNS:
nslookup rrrrr.com
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: rrrrrr.com
Address: 54.88.87.161
Is there any way that I can debug this? It has been going on several days.
The question is not resolved absolutely, but the problem appears to be with the GoDaddy DNS Servers. The problem appeared to be continuously growing and their technical support denied that anything was wrong - "appears to be a localized issue with some ISPs".
So I added for now backup DNS with Namecheap.com
Also useful is this post:
http://rscott.org/dns/GoDaddy_Selective_DNS_Blackouts.htm
I am able to access my site but it appears DNS isn't being resolved correctly, meaning it takes forever for the site to be found. Once its located the site performs as expected, but if I were to wait a few minutes and try to retrieve the site once more, it again takes a long time (20+secs) to resolve. This is for production, and not a local development. Note: If I go to to my servers elastic IP (54.245.124.102) my site loads instantly.
Route 53
NAME: example.com.
TYPE: A
VALUE: 54.215.114.102 - 10.252.55.133
TTL: 7200
NAME: example.com.
TYPE: NS
VALUE: ns-1043.awsdns-12.org. - ns-1709.awsdns-11.co.uk.
TTL: 7200
The problem I was experiencing was that there was a coin flip chance of getting either IP address. 10net(10.x.x.x) IP addresses are not routeable over the internet, people outside of my local network could reach the 10net address. This was causing dns resolution times to be slow.
I have a primary and secondary domain controller that we use as our DNS servers. Users are getting mixed results with accessing websites. Some work fine, others are giving an error:
Network Access Message: The website cannot be found
Explanation: An IP address for the website you requested could not be found.
As a result, it was not possible to access the site.
For example, mcmaster.com will not work. If I run nslookup from the primary DC:
C:\Users\Administrator>nslookup mcmaster.com
Server: dc.mydomain.local
Address: 10.1.1.35
Non-authoritative answer:
Name: mcmaster.com
Address: 209.64.25.230
All looks well, but when I run nslookup with www. prepended to the address:
C:\Users\Administrator>nslookup www.mcmaster.com
Server: dc.mydomain.local
Address: 10.1.1.35
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dc.mydomain.local timed-out
Running nslookup www.mcmaster.com from the DC gives a different error:
*** backupdc.mydomain.local can't find www.mcmaster.com: Server failed
I think that mcmaster.com resolves to www.mcmaster.com, which results in the user not being able to access the site. Any ideas how I can troubleshoot this?
I ran an nslookup from my system at work and got the following response:
Server: WHATEVER
Address: xxx.xxx.xxx.xxx
Non-authoritative answer:
Name: mcmaster.com
Address: 209.64.25.230
Server: whatever
Address: xxx.xxx.xxx.xxx
Non-authoritative answer:
Name: a1843.b.akamai.net
Addresses: 23.66.232.17
23.66.232.26
Aliases: www.mcmaster.com
www.mcmaster.com.edgesuite.net
My initial thought was whoever owns DNS for Mcmaster simply didn't have www as a valid response. I know I forward requests to www.whateverdomainirun.com to whateverdomainirun.com, but, seeing different DNS for the two surprised me.
When I navigate to http://mcmaster.com I get forwarded to the www. When I run a tracert on mcmaster.com it fails with Destination net unreachable. It looks to me like this company has put their site in Akamai's hands and either that's recent so your local DNS servers haven't updated and you could try flushing the cache and doing it again, or, in some way you're blocking requests to Akamai for some reason on your firewall.
Best and quick guess for you and it may be wildly wrong :).
I am new to BIND, and thought I had a grip on DNS, but obviously I was mistaken.
BIND is installed on Windows Server 2008 Web
I created a zone (example.com) with Dyn.
I registered the domain for that zone successfully, using the Dyn nameservers
I created two subdomains (A records) on the Dyn zone: ns1.example.com and ns2.example.com
Each subdomain points to a unique IP, bound to my server where BIND is listening
When I query ns1.example.com with nslookup, for the a new domain I created on that webserver, it returns ns1 with its ip, but gives the following error:
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns1.example.com timed-out
If I run nslookup on the webserver itself, with the same query, I get:
> example.com
Server: ns1.example.com (which is the slected nameserver)
Address: xx.xx.xx.xx
Name: example.com
Address: xx.xx.xx.xx
It might be worth mentioning, that the Webserver is located in the UK, and I am located in South Africa.
My registrar, in South Africa, returns the following when I try to register domainxyz.example:
The SOA record for domainxyz.example at xxx.xxx.xxx.xxx can not be retreived.
The most common reasons for this is that the Nameserver is not currently
reachable or the Nameserver has not been configured for this domain.
I can ping and resolve ns1 and ns2 from my pc, where the nslookup fails.
After a long discussion with myself, and curiously reviewing my post... I decided I must be really burnt out.. and I opened UDP port 53 on my windows firewall on the server.
Tadaaa.....works!
Sometimes it helps bouncing something off someone, even if its a lonely sunday night web page /forum.
Maybe this helps someone else in the future. This whole new web server commisioning has so many aspects to configure, and I lost site of the basics.
Cheers, and thanks..!
I seem to be having some issues with my domain controller when trying to resolve hostnames using dns. It does seem to work but it always takes a couple of attempts, even if its a hostname i have already resolved. I have been noticing it with webpages and downloads.
Here is a nslookup test i did
C:\Users\chris.townsend>nslookup abc.com
Server: dc.example.com
Address: 192.168.101.20
DNS request timed out.
timeout was 2 seconds.
*** Request to dc.example.com timed-out
C:\Users\chris.townsend>nslookup abc.com
Server: dc.example.com
Address: 192.168.101.20
Non-authoritative answer:
Name: abc.com
Address: 199.181.132.250
Some sites it works first time and some it takes a couple more. I cant seem to figure it out and its the same on all the systems in our office. Restarting and /dnsflush dont seem to make any diffence either.
Can anyone suggest anything?
just incase anyone else has this same issue : this is what we found out it was - we use a watch guard router and it seemed to be proxies causing this issue