DNS manager allows adding of linode.com
Domain Zone Purpose Last Modified Last Generated Edit Remove Status Check
frankish.com.au master 2006-10-30 06:12:29 PM 2006-10-30 06:12:29 PM (generate) Edit Remove ACTIVE check
our-lan.com master 2006-10-26 07:48:23 PM 2006-10-30 07:48:23 PM (generate) Edit Remove ACTIVE check
linode.com master 2006-10-30 06:14:07 PM -never- (generate) Edit Remove ACTIVE check
Granted i deleted it before it generated so not sure what the results were, but i would assume that it probably shouldnt have let me add linode.com in the first place.. actually i would imagine i shouldnt be able to add the domains of anyone that already has added the domain in to the linode.com servers
cheers
NF
5 Replies
It works the same for all domains, and in that way, only people who change the DNS servers listed in their whois information to point to us will actually be served by Linode's nameservers.
Also, yes, domains can be added only once across all active domains managed by us.
-Chris
or was that general information on how name server lookups happen?
@Internat:
Is that saying that the ns{1,2}.linode.com name servers check if the whois info points to them before serving any data for it?
or was that general information on how name server lookups happen?
The latter.
HTH,
-Chris
linode.com. 1764 IN NS ns2.theshore.net.
linode.com. 1764 IN NS ns1.theshore.net.
linode.com. 1764 IN NS ns0.theshore.net.
linode.com. 1764 IN NS ns.theshore.net.
linode.com. 1764 IN NS ns3.theshore.net.
It wouldn't have affected anyone, unless for some strange reason they were using ns{1,2}.linode.com as their resolver.
@CryptWizard:
It wouldn't have affected anyone, unless for some strange reason they were using ns{1,2}.linode.com as their resolver.
mwalling@you ~$ dig @ns1.linode.com google.com
; <<>> DiG 9.4.1-P1 <<>> @ns1.linode.com google.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 55973
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
… which wouldn't work anyway.