Is there a standard time duration before DNS caches are cleared, so that if a distracted operator or stuck key turns a TTL of 86400 into 864000000 you don't end up with an authoritative resource record or even entire DNS zone whose changes won't be recognized for 27.397 years?
And, if there is no protection against this sort of error, then what is the reasoning behind allowing TTL duration up to 68 years instead of a maximum value of perhaps one month?
I bought a domain for us to use to hide ugly staging URL's (like what Azure gives you for staging).
I pretty exlusively only buy domains from MyDomain.com, but I might have bought this one from NetworkSolutions.com as a test (as we had a client having trouble with them, we wanted to walk their footsteps).
Now when I look for this domain it is with neither host. When I WHOIS this domain it says that it's owned by "Click and Name"... I went to clickandname.com and this is definately not a site I have ever visited before.
The domain is still active for me and the ICANN info still points to me. I even got renewal notifications from Click and Name to renew, but these emails don't point me to any site. Any help before I approach these guys (that I don't trust)?
Edit:
I didn't give a great timeline of this... I would have bought this about 10 months ago, and I've now started getting these renewals from a company I know I didn't register with. Of which, the WHOIS inforation says these guys own my domain. This is why I don't quite remember who I registered this with. I've looked back through invoices to no avail.
Say I've operating ns1.example.org and ns2.example.org on which I want to host the zone file for example.com
When I go to my registrar and purchase example.com , I will tell my registrar that my nameservers are ns1.example.org and ns2.example.org
My question then is, why do I then also need to specify those nameservers in the zone file for example.com ? Haven't I already told the .com nameservers where to lookup information on example.com , making the NS records redundant?
Clearly I'm missing some crucial fact...
What are the practical benefits and downsides of running your own DNS server instead of using the DNS servers provided by your registrar? More specifically, in what situations would you run your own DNS server?
Let's that I've got the domain mydomain.com.
I want that when any visitor goes to
www.mydomain.com
xyz.mydomain.com
abc.mydomain.com
asd.mydomain.com
qwe.mydomain.com
etc...
the visitor will continue seeing "xyz.mydomain.com", but the real address will be "mydomain.com". my asp.net application will handle the differences between the addresses. I want that the subdomain can be anything.
The problem is: I'm using a shared host. They allow me to create subdomains and allow me to create some DNS records:
Address (A)
CNAME
Mail (MX)
IPV6 (AAAA)
TXT
Is it possible to set up my hosting to accept that asterisk/wildcards for subdomains? How do I do it?