named and database backed systems
Hello, my past post about wildcarding the . in a named server seems it may be wrought with issues in the long term. In short, my issues is a auto website creation tool that needs to be simple for users to change their registrar data, and have their site be served up. The old method works, but is being outgrown, I can come in and try to solve it with scripts to sync the website to local named files, but it will always be a battle. I am coming up short on finding any database backed store for named. I think sqllite would be the best for raw performance, but then again, even a million records in mysql is trivial. I am just worried about volume of selects. Can anyone point me to any info on database backed named solutions? Thank you named users, you are all very helpful. -- Scott ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: named and database backed systems
Use the DLZ extension. It's been around for a while.
I.e. put the following in your named.conf and use whatever interface you
wish. I use Ant with a few modifications. I don't have nearly the
number of domains that you do so my simple system works fine.
dlz postgres zone {
database postgres 2
{host=localhost dbname=dns_data user=bind password=xx}
{SELECT 'TRUE' FROM canonical WHERE lower(content) =
lower('%zone%') limit 1}
{SELECT ttl, type, priority, data FROM record, canonical WHERE
lower(content) = lower('%zone%') AND host = '%record%' AND zone = domain}
{}
{SELECT ttl, type, host, priority, data FROM record, canonical
WHERE zone = domain AND lower(content) = lower('%zone%')}
{SELECT 'TRUE' FROM xfr, canonical WHERE zone = domain AND
lower(content) = lower('%zone%') AND client = inet '%client%'};
};
Rather spiffy for centralizing your record store with immediate change
visibility.
-david
Scott Haneda wrote:
Hello, my past post about wildcarding the . in a named server seems
it may be wrought with issues in the long term.
In short, my issues is a auto website creation tool that needs to be
simple for users to change their registrar data, and have their site
be served up.
The old method works, but is being outgrown, I can come in and try to
solve it with scripts to sync the website to local named files, but it
will always be a battle.
I am coming up short on finding any database backed store for named.
I think sqllite would be the best for raw performance, but then again,
even a million records in mysql is trivial. I am just worried about
volume of selects.
Can anyone point me to any info on database backed named solutions?
Thank you named users, you are all very helpful.
--
Scott
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Linux: freedom to build is good
Please top-post and trim when replying to my messages. I most often read mail
on a small device.
VERY NOT-IMPORTANT NOT-LEGAL NOTICES:
Recalling a message does in no way delete it from my computer. Rather, it
brings attention to your original email and recalling it causes me to search
for a reason to find embarrassment. Please don't send message recall messages.
It's silly and obnoxious and wastes even more bandwidth and patience.
Regardless of what legal message you append to your email message, I am not
obligated or constrained in any way shape or form. If I feel like printing it
outand taping it up at the local gym, or mass mailing it to 15,000 people, I
will. I feel especially inclined to do so the longer your legal advisory is.
Such notices are unenforceable and do not protect you or your company from
things you say, or things others do with the email.
Millions of innocent men, women and children, since the introduction of
Christianity, have been burnt, tortured, fined, imprisoned; yet we have not
advancedone inch towards uniformity. What has been the effect of coercion? To
make half the world fools, and the other half hypocrites. --Thomas Jefferson
This message is confidential to the Internet at large, unless otherwise
indicated or apparent from its nature. It may not be reproduced on Mars unless
it has previously been printed on Uranus. This message is directed to the
intended recipient only (usually everyone, but sometimes nobody and once in a
blue moon, just somebody), who may be readily determined by the sender of this
message and its contents. This email message (including any attachments) is not
for the sole use of the intended recipient(s) and may or may not contain
confidential, proprietary and privileged information. It may include sarcastic
holier than tho content. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient: (a) any dissemination or copying of this message is
strictly prohibited unless you feel otherwise; and (b) immediately notify the
sender by return message (but only if the sun has gone black) and de
stroy any copies of this message in any form (electronic, paper or carved in
stone) that you have. Please destroy by smashing your computer with a 21lb
sledge hammer approximately 17 times to ensure destruction of your system. Any
unauthorized review, use, disclosure or distribution is most assuredly not
prohibited and you will not IMMEDIATELY be PROSECUTED to the fullest ... or
emptiest ... extent of the law. If you are not the intended recipient, please
immediately notify some random person of your age, sex, and location and your
undying desire to fornicate with them by email and destroy all copies of the
original message if you sent it to an underage person. Oh, and definitely
don't tell me about it. The delivery of this message and its information is
neither intended to be nor
Re: named and database backed systems
Damnit, ever time I search this stuff out, I search for named
something-or-other and should use BIND in my search :)
I am going to test deploy on my worksation on OS X. Named comes up
with relative ease, just add a key and I am pretty much up and
running, albeit out of date, but for testing, I am ok with that.
Are you telling me I need not even build named to get DLZ support? It
is just there already?
I see you are using postgress, mysql or sqllite should not be an issue
either?
Zones are backed in DB, but not queried in real time are there? If
they are, I can see, sub 50ms return times going way up.
Thanks for pointing me in the right direction, I will go read the DLZ
pages now.
On Jan 28, 2009, at 10:25 PM, David Ford wrote:
Use the DLZ extension. It's been around for a while.
I.e. put the following in your named.conf and use whatever interface
you
wish. I use Ant with a few modifications. I don't have nearly the
number of domains that you do so my simple system works fine.
dlz postgres zone {
database postgres 2
{host=localhost dbname=dns_data user=bind
password=xx}
{SELECT 'TRUE' FROM canonical WHERE lower(content) =
lower('%zone%') limit 1}
{SELECT ttl, type, priority, data FROM record, canonical WHERE
lower(content) = lower('%zone%') AND host = '%record%' AND zone =
domain}
{}
{SELECT ttl, type, host, priority, data FROM record, canonical
WHERE zone = domain AND lower(content) = lower('%zone%')}
{SELECT 'TRUE' FROM xfr, canonical WHERE zone = domain AND
lower(content) = lower('%zone%') AND client = inet '%client%'};
};
Rather spiffy for centralizing your record store with immediate change
visibility.
--
Scott
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: named and database backed systems
In message 29c7b7bc-f017-4404-b011-8b50206c7...@newgeo.com, Scott Haneda writ
es:
Damnit, ever time I search this stuff out, I search for named
something-or-other and should use BIND in my search :)
I am going to test deploy on my worksation on OS X. Named comes up
with relative ease, just add a key and I am pretty much up and
running, albeit out of date, but for testing, I am ok with that.
Are you telling me I need not even build named to get DLZ support? It
is just there already?
You have to tell configure that you want it. It's still
contributed code.
I see you are using postgress, mysql or sqllite should not be an issue
either?
Zones are backed in DB, but not queried in real time are there? If
they are, I can see, sub 50ms return times going way up.
Thanks for pointing me in the right direction, I will go read the DLZ
pages now.
On Jan 28, 2009, at 10:25 PM, David Ford wrote:
Use the DLZ extension. It's been around for a while.
I.e. put the following in your named.conf and use whatever interface
you
wish. I use Ant with a few modifications. I don't have nearly the
number of domains that you do so my simple system works fine.
dlz postgres zone {
database postgres 2
{host=localhost dbname=dns_data user=bind
password=xx}
{SELECT 'TRUE' FROM canonical WHERE lower(content) =
lower('%zone%') limit 1}
{SELECT ttl, type, priority, data FROM record, canonical WHERE
lower(content) = lower('%zone%') AND host = '%record%' AND zone =
domain}
{}
{SELECT ttl, type, host, priority, data FROM record, canonical
WHERE zone = domain AND lower(content) = lower('%zone%')}
{SELECT 'TRUE' FROM xfr, canonical WHERE zone = domain AND
lower(content) = lower('%zone%') AND client = inet '%client%'};
};
Rather spiffy for centralizing your record store with immediate change
visibility.
--
Scott
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
