Hot answers tagged nameserver
42
They're 13 highly available clusters of servers, not simply 13 servers.
Among other things, root nameserver operators are required to have enough capacity to handle three times their normal traffic load (RFC 2870). This leads to rather large clusters.
However, the root nameservers only serve responses for the top level domains themselves, i.e. com., net., ...
19
The diagnostic text from Pingdom is exactly correct. TCP is not just for zone transfers.
DNS server implementations are now "required" (in so much as any RFC requires anything) to support TCP, per RFC 5966, "DNS Transport over TCP - Implementation Requirements".
Note that this is a requirement on the server software implementation, it does not strictly ...
14
The requirement to run two nameservers comes from ยง4.1 of RFC 1034, and is indeed for redundancy.
There are numerous providers who will offer you very cheap "secondary DNS" service where they transfer the zone file from your primary server using AXFR. For example, in the UK we have a well-known provider who'll do secondary service for 50 domains for just ...
14
That's not an IP address, it's a very, very invalid FQDN. In other words, it's a string of characters rather than an actual address. The dot at the end of the IP address gives it away, along with the specs in the RFC that state that an NS record answer is a string.
Interestingly, I just checked the domain you gave and it's already been fixed up to use ...
13
Note that which server the clients will hit depends on resolver implementation. Some resolvers will strictly go for NS1, some will randomly chose NS1 or NS2. In either case if the server responds they will not try the other server. The only time they try the other server is when the first server is unable to serve the request.
To have a look at a more ...
11
4.2.2.2 is pretty long in the tooth.
If you're wondering why it has a PTR record of gtei.net then here's a little history.
It was originally owned and hosted by a provider called BBN Planet.
BBN was acquired by the General Telephone & Electronics Corporation in 1997 and became a sub-division of GTE known as GTE Internetworking. Hence the GTEI domain.
...
11
I've worked with djbdns in the past and currently run a bunch of BIND servers.
The biggest problem with djbdns is best put the way my first grade teacher put it on my report card: "doesn't play well with others". It simply doesn't behave like anything else on a unix box in all sorts of very small ways that can bite you later. It uses a syntax for zone ...
11
Yes, you can, if your registrar supports IPv6 glue records.
However, if you're only delegating to the IPv6 record, then IPv4-only clients can't query your server. Probably an unwise decision at this point in the world's deployment of IPv6.
Anyway, all this does is circumvent that pingdom tool's check on having two name servers. The reason that check ...
11
No you don't because DNS records don't propagate. What you do need to allow for is for any cached records to expire, based on the TTL of the record in question.
If this is a new record, no caching can have occurred so the new record should be available and should resolve immediately.
Additionally, the root servers (first level; .) don't host DNS zones or ...
9
They don't. The root nameservers just have to tell you what nameservers handle com. From then on, you don't need to go to them to handle any domain inside com. The root nameservers have no idea who owns example.com. They're root nameservers, not com nameservers.
What slimsuperhero said is also true. Many high-volume nameservers use anycast to have a single ...
9
You shouldn't really have to notify anyone, beyond your own domain registrar.
If you intend to have nameservers at 2.2.2.1 and 2.2.2.2, just make certain that they only serve the names for which they are authoritative, and nothing else. Pretty quickly, clients of the old nameservers at 2.2.2.[12] will realize that they're not getting responses, and they'll ...
8
You don't need to do anything complicated.
As soon as your new ISP has told you what your new IP range will be you can request which PTR records should be put on each IP address.
Once you've moved, you can tell the old ISP that you no longer require them to maintain PTR records for you.
That's it. There's no "harm" in having both sets of IPs having the ...
8
If it is for yourself, and if you want to learn how DNS works, I'd use djbdns.
If you want to understand how everyone else does DNS, and how to support typical enterprise deployments, learn bind.
If your goal is minimal effort and support, and you're reasonably competent, djbdns has a far lower support overhead.
If you're more on the novice side of the ...
8
As others have commented, there are multiple nameservers for redundancy purposes.
If you have a single DNS server and it goes down, all your services go down with it regardless (er, whichever services rely on IP name resolution at least). If you have multiple name servers then when one fails the other(s) will take over or at least be reachable.
Without ...
8
We moved recently and had all sorts of problems with DNS.
When we did the swing over most customers started hitting the new IPs right away. But some were still hitting the old IPs for weeks. We left a server up for a month or so. Eventually we went through the IIS logs on the old machine and called the customers telling them to flush DNS on there company ...
6
Log into the godaddy.com portal and edit the domain you want to change the DNS settings for (You are looking for the domain Manager).
In the host summary (bottom left) is where you need to add the entries to ns1 and ns2 along with their IP addresses.
It'll then take a little bit for everything to replicate so that you can point other domains to those ...
6
If you don't want to create another IP, then all you can do is install a reverse http proxy on the main IP and a name based virtual host to route the traffic using mod_proxy.
Here is how you can do it with apache, almost any http server can do it, other popular alternatives are squid, nginx, lighthttpd, etc.
Listen IP_ADDR:80
NameVirtualHost ...
6
You can create a CNAME record that points to the EC2 Public DNS
In the GoDaddy DNS manager:
Set record type to: CNAME
Domain name to: whatever.domain.com
Canonical name to: ec2-your-ec2.compute-1.amazonaws.com
Then you can access ec2-your-ec2.compute-1.amazonaws.com using whatever.domain.com
This will same you from having to pay the $.01 per hour for ...
6
There is no A record for ameeto.com.
There is no record whatsoever for www.ameeto.com
These are fundamental errors: The DNS system cannot return information that does not exist.
Correct these problems (Create entries in your DNS zone. Contact your ISP for help) and see if your site starts working...
;; global options: printcmd
;; Got answer:
;; ...
6
There are two primary ways to do this, neither of which involves the ping tool.:
Look at the whois data.
This will typically include a section titled something like "Domains servers in listed order", which lists your nameservers.
dig -t NS mydomain.com
This will report the NS records that your local nameserver gets when it tries to resolve mydomain.com.
...
6
DNS records doesn't propagate in the sense that they aren't "pushed" from your server to other resolvers. What actually happens is that when other DNS servers look up your domain, they cache the record for X seconds so that they don't have to do another lookup for subsequent requests. X seconds should be determined by the TTL value on the record when it was ...
6
This is obviously a staged Q&A, but this tends to confuse people often and I can't find a canonical question covering the topic.
dig +trace is a great diagnostic tool, but one aspect of its design is widely misunderstood: the IP of every server that will be queried is obtained from your resolver library. This is very easily overlooked and often only ...
6
The answer to the main question is "no, they don't". Your two (or, indeed, more) nameservers can (and probably should) be hosted with separate companies, in separate datacentres, preferably served by different network providers.
How you set up your 2ary nameserver is slightly beyond the scope of an SF answer - it depends on what resolver you're running, or ...
6
My preliminary research indicates the answer is yes. Using dig <domain> +trace I've been noting the time that the relevant top level name server takes to return the nameservers from the next step (in most cases, the step that returns ns1.someisp.com and ns2.someisp.com).
While a surprising number of queries both for .au domains and .com domains come ...
6
Whois lists your name servers as amy.ns.cloudflare.com and cody.ns.cloudflare.com, but the parent servers (the gTLD servers) list ns1.netregistry.net, ns2.netregistry.net and ns3.netregistry.net as well as amy.ns.cloudflare.com and cody.ns.cloudflare.com as the name servers for your domain.
You need to fix this at your domain registrar as they're the party ...
6
The nameserver which resolves the PTR records for that subnet is ns1.ghostdns.de which, I'm guessing, you do not operate. It looks like it is operated by hostmaster@ghostnet.de.
You need to contact whoever does operate that nameserver and ask them to add a PTR entry for 137.214.249.94.in-addr.arpa.
$ dig -x 94.249.214.137 -t SOA
; <<>> DiG ...
5
Technically what you're asking for is invalid. CNAME conflicts with all other records (with a special exception for DNSSEC records), thus having CNAME xxxxx conflicts with the SOA, MX, NS etc records for the domain. My guess is that the reason the domain resolves when you use an A there and fails when you use CNAME is because the DNS server enforces those ...
5
An authoritative Nameserver is a nameserver (DNS Server) that holds the actual DNS records (A, CNAME, PTR, etc) for a particular domain/ address. A recursive resolver would be a DNS server that queries an authoritative nameserver to resolve a domain/ address.
So, for example, If I have a a DNS server in my network that holds an A record for foobar.com, ...
5
There isn't a predictable order to how authoritative name servers are queried. With the setup you described, if ns3.freedns.ws doesn't have a record for your domain name then roughly 1/3 of the visitors trying to get to your site will be unable to because the name server will respond that it does not have an IP address for your domain name. I'd suggest ...
Only top voted, non community-wiki answers of a minimum length are eligible
