Excuse any spelling. I'm mobile.
I would be wildcarding "."
My client has a website building service. You get a free account and
tools to get your site online all built in a browser with web based
tools.
It works well now but the synchronization of the database with named,
users coming and going, keeping a slave up to date, delete zones, all
that is a burden.
All the time the users need status of their domain. Where the whois is
at, if their zone has been created etc.
It works, they have growing pains. It us only in private test and
growing fast. Free seems to be appealing :)
Since users sign up they must change their ns's at their registrar.
They own their domains. They can leave at any time. The service does
not offer registration.
I can remove the entire DNS management, zone creation, and deltion if
I wildcard. Any domain in which they enter in my clients ns's will
resolve automatically as soon as the whois updates.
So yes, these two ns's would be authoritative for all domains, but if
I understand it correct, only those that users so chose to.
It's not like an end user would request amazon.com and ever hit these
two ns's. If that could happen DNS would be easily messed with.
The ns's would deny recursion, they of course would not be used as a
local resolved either. As a matter pf fact recursion would be denied
to all nets entirely.
I hope this explains it better. While this is not domain parking, it
acts much like it, I would guess large registrars do something
similar. I can not imagine them generating all these real zone files
in such quantity for every parked domain.
I'm trying to bring reliability in the synchronization of services
trying to be offered.
Thanks fly any suggestions.
--
Scott
Iphone says hello.
On Jan 28, 2009, at 8:44 AM, "Ben Bridges" <bbrid...@springnet.net>
wrote:
What specifically are you intending to wildcard? "com."? "net."?
"."?
If so, then you would be implicitly making your name servers
authoritative for domains for which your servers are not supposed to
be
authoritative.
Ben Bridges
-----Original Message-----
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Scott Haneda
Sent: Wednesday, January 28, 2009 3:31 AM
To: bind-users@lists.isc.org
Subject: wildcarding everything
Hello, I am wondering the technical possibility of a DNS
change. Even if it is technically possible, I also want to
make sure it is compliant as well.
I would like to resolve any and all requests to a fixed IP,
if there is no zone in place. While I understand I can
create a zone for *.example.com and resolve all of the *
portion to an A record and further have a web server take over...
What I am looking to do now, is have the very act of having my two
NS's listed as NS's with their domain, resolve to an A record.
Essentially, wildcard the entire DNS machine.
There may be cases where a real zone is put in place, to a
different A record, and that would need to take priority, but
if it does not, I would like to resolve it.
The NS's in question will not be answering for recursive
queries, so I am not worried about local requests getting
hijacked or mis-routed.
An example would be:
some-domain-foo.com is registered. My NS of ns-me.example.com
is set up and working, but does not have some-domain-foo.com
entered as a zone. When a request comes in for
some-domain-foo.com I want an A record for an IP of my
choice, also for www.some-domain-foo.com as well.
Possible? Acceptable?
Thanks.
--
Scott
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
