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.
Related
In the last month, my site no longer works on my computer or any computer connected to the same network that I use at home and I have tried other internet networks and the site doesn't work too, but strangely it works in some other networks!
The error message in the browser is : ERR_NAME_RESOLUTION_FAILED
I did not know the problem but when I looked at the site intoDNS I found 3 problems :
WARNING: One or more of your nameservers did not return any of your NS records.
------
You should already know that your NS records at your nameservers are missing, so here it is again:
ns77.domaincontrol.com.
ns78.domaincontrol.com.
-------
ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
208.109.255.49 216.69.185.49
Also, two months ago I moved my domain from Godaddy to Namecheap.
Please can you help me?
The domain's name servers are pointed to the servers of Godaddy, but there is no DNS zone for the domain there. You need to check what are the name servers of Namecheap (or another DNS hosting service) and point the name servers of the domain to these servers. Also you will have to create a DNS zone for the domain at the new DNS host (Namecheap or other of your choice) and create DNS records pointed to your web host's IP address.
If you only have a web site and no other services, like mail server you can only create two A records, like this:
Type: A
Host: # (or empty, it means the same)
Target (or Value, or Points to): ip.of.web.site
Type: A
Host: www
Target: ip.of.web.site
I am in the process of moving the website traffic for adadarters.com from old host to new host. We are keeping old host for various reasons, including mail and ASP files that we don’t want to move, so I simply modified the A record to point to the IP for new host. After 10 hours it has still not really propagated, even though it appears that it has. I have been doing ipconfig /flushdns all day.
What’s happening is that adadarters.com serves up the NewIP (74.220.215.66) and www.adadarters.com serves up the OldIP (65.254.231.127). If you try and type in the URL without www, it appears to redirect to www and sends you to old host.
The way I figured out was nslookup adadarters.com 205.171.3.66 (my ISPs IP address) vs nslookup www.adadarters.com 205.171.3.66.
Also, a traceroute to adadarters.com vs www.adadarters traces the route to new and old IP addresses.
New host says DNS looks fine to them. Old host says settings look fine to them too, and that I just need to wait longer for it to propagate. But why would www propagate differently than non-www? I think they are just putting me off because they don't know (one reason they are the old host).
Any ideas about what might be happening?If by some chance this has resolved by the time you look, the old host files have the logo on right, new has logo on left and is a WordPress site.
This is off-topic here, you should've asked on https://superuser.com/
Your computer probably cached the old DNS. Try ipconfig /flushdns
The problem clearly is not in your ISP's DNS:
$ nslookup www.adadarters.com 205.171.3.66
Server: 205.171.3.66
Address: 205.171.3.66#53
Non-authoritative answer:
Name: www.adadarters.com
Address: 74.220.215.66
Hopefully someone can help clarify this.
I have a domain ie example.com registered with Go Daddy. I host the website with TSOHost so in my domain configuration, I have set the following NS records.
Nameserver 1: ns1.tsohost.co.uk
Nameserver 2: ns2.tsohost.co.uk
I am now able to serve the website both www and non www from this hosting package. I simply have an A record for example.com and a CNAME for www.example.com to point to example.com (this is being configured in the cpanel Advanced DNS Zone Editor). So now we have the website showing as expected and required.
I would also like to setup a kind of DDNS service using a different server entirely, (this will hold DNS records that I will create on the fly using a Radius database).
So I want to use the subdomain ddns.example.com for this DDNS service, ie bob.ddns.example.com for Bob (so that when I ping bob.ddn.example.com, I can alter the IP to 8.8.8. say). In Cpanel I have an A record for ddns.example.com and an A record for *.ddns.example.com to point to my server that will manage this, for example 85.214.214.214.
I have installed Bind on the server (currently using a digital ocean server for this, to which I have added ddns.exmaple.com as an A record to the droplet and *.ddns.example.com also), I have created a zone for ddns.example.com, within this I have set the ns record as the digital ocean details.
I have then added the following to my file /var/named/ddns.example.com.hosts
$ttl 38400
ddns.example.com. IN SOA ns1.digitalocean.com. jon#example.com. (
1414575123
10800
3600
604800
38400 )
ddns.example.com. IN NS ns1.digitalocean.com.
bob.ddns.example.com. IN A 8.8.8.8
When I ping bob.ddns.example.com on the server with bind installed I get 8.8.8.8, but when pinging for anywhere else I get the bind server IP.
Can I ask if what I am doing is possible ie, going from godaddy to tso, to another server and if so what NS records should I specify for bind? or is there something in the named config I need to change, I have set the following options in named.conf in an attempt to solve this issue.
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
recursion yes;
I am aware that recursion may leave me open to DOS attacks and I intend to turn this to no eventually, but for the moment during testing I have left this to yes.
Any help or information would be greatly appreciated, I have been trying different variations of zone files etc without success, I am really though unsure as to if I am going in the right direction.
Hopefully I have made sense, but any further info I can provide, please let me know.
My first question would be - Are you sure you've updated the Registrar with this server as the DNS nameserver for this domain?
Use nslookup to find out:
# nslookup
> set querytype=NS
> server 4.2.2.1 (a DNS server on the Internet)
> ddns.example.com. (a closing dot helps avoid lookups using preferred search domains.)
and confirm that the Internet knows who to communicate with, and that your NS host is authoritative for the domain.
Next would be - Do you have any other nameservers up to "answer" for that subdomain, causing other problems?
BTW - glad to hear you fixed this issue!
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..!
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.