[users] List moving to SourceForge
All, I'll be shutting down this list this weekend. I've set up a replacement on SourceForge (where the rest of this project is) here: https://lists.sourceforge.net/lists/listinfo/vegadns-users If you wish to remain on this discussion list, please go the the URL above and sign up for that list. There's no import feature, I'm afraid, so you need to sign up over there. Thanks! Bill Shupp
Re: [users] where is latest stable
On Feb 17, 2009, at 11:59 AM, Just Nulling wrote: Hi, where is the latest stable version of vegadns? sf.net has 0.9.10 and projects.robinbowes.com has rev 67 Both don't work for me. 0.9.10 shows domains but I can't view/edit any records rev 67 works much better (after some minor weaks for image/css location) can view/edit domains and records but get Error: illegal mode when click registration or upload links. Not sure what are this links are used for anyways. The official stable is on sf.net. But I am no longer maintaining VegaDNS, and have ceased work on the 1.1.x tree due to lack of time. Robin, ping me if you are still developing on VegaDNS and want to move your work to sf.net so that it's all in one place. Thanks, Bill Shupp
Re: [users] Using version in svn
On Jul 9, 2008, at 7:58 AM, Robin Bowes wrote: Robin Bowes wrote: Bill, Is the version in svn trunk ready for use yet? Bump. Bill? Nope. You're certainly welcome to play with it, but it's pretty broken. I was about 60% through a significant re-write when I took a job here at Digg. I've not had much time to work on it recently, unfortunately. Regards, Bill
Re: [users] PTR records
On May 20, 2008, at 2:44 AM, Dimitri P. Alexandris wrote: I use version 1.1.6. This version is marked devel status, and is not meant for production. Since people keep downloading it and posting about it, I've removed it from SourceForge to eliminate confusion. This branch will not be developed further, it has been replaced with a near rewrite that is still only in subversion. Regards, Bill
Re: [users] hack
On Feb 25, 2008, at 3:03 AM, Michael Christie wrote: Hi all just letting you all know that i had vega dns version 0.9.9.1 hacked on me. the attacker installed a file in the /src dir and some how set up a cron to run the script it was some kind of spam email hack. Now i am back to hand coding the data file until i can work out how to lock it down more. Micheal, Please provide as many details as you can. Thanks, Bill
Re: [users] vega dns
On Feb 23, 2008, at 4:47 PM, Michael Christie wrote: hi there , I have been using vega dns and tiny dns for a long time now and had no problem with the install and set up. I have just set up a new server in the past weeks and installed tiny dns using the data file from the old server all works fine. last night i installed vega dns on the server all worked well with the installation and web access was fine . i set up the new zone and run update-data.sh check the data file and did a dig on the zone. I am finding that the zone will not respond to dns query's, it is like the server is not responding , the new vega dns data file looks the same as the old one, i then copy the old data file back and run make, then dig the server all works ok with the old data file. can any one here help with this, and advise me what is going on. You might need to update the IP address of the ns records to work on the new system. Regards, Bill
Re: [users] vega dns
On Feb 20, 2008, at 2:26 PM, Scott Muller wrote: Michael Christie wrote: Hi all, I have been useing vegadns for a long time on a freebsd box. I have been unable to run update-data.sh from the cron. the updatedata-sh will run from the comand line. can any one help solve this. Michael, From memory I had to put the full path to wget into the script for it to work. Right. It might not be in cron's path. Also make sure the user the script runs as has permissions to write to the djbdns data files. Regards, Bill
Re: [users] SOA Serial Numbers
Jason 'XenoPhage' Frisvold wrote: Bill Shupp wrote: I chose to use tinydns default serial numbers. I believe the 1.1.5 series has custom serial support. But I haven't looked at it in a while. Is 1.1.6 considered production quality? No, it has major internal changes that are not complete. Regards, Bill
Re: [users] Difficulty getting started...
Robin Bowes wrote: Hi, I'm just checking out vegadns and am having trouble getting started. I on a FC4 platform with: httpd-2.0.54-10.3 php-5.0.4-10.5 mysql-4.1.16-1.FC4.1 I started by trying the 1.1.5 dev release. All seemed to go well, and the first screen appears requesting that I Please edit your account settings for the initial 'senior_admin' However, when I enter the new values, and hit edit I get this error: Error: passwords do not match (believe me - they do!) I then dropped the vegadns database and started again, only instead of changing the default values I logged out. So, I should be able login using the default settings of test@test.com / test. When I try that I see the following error: Error signing on: incorrect email address or password Any idea what's going wrong? Are there any particular PHP settings that I need to have set or unset? Don't use 1.1.5 unless you are developing. There are several incomplete areas. Use 0.9.9.1. Regards, Bill
Re: [users] Difficulty getting started...
Bill Shupp wrote: Robin Bowes wrote: Hi, I'm just checking out vegadns and am having trouble getting started. I on a FC4 platform with: httpd-2.0.54-10.3 php-5.0.4-10.5 mysql-4.1.16-1.FC4.1 I started by trying the 1.1.5 dev release. All seemed to go well, and the first screen appears requesting that I Please edit your account settings for the initial 'senior_admin' However, when I enter the new values, and hit edit I get this error: Error: passwords do not match (believe me - they do!) I then dropped the vegadns database and started again, only instead of changing the default values I logged out. So, I should be able login using the default settings of test@test.com / test. When I try that I see the following error: Error signing on: incorrect email address or password Any idea what's going wrong? Are there any particular PHP settings that I need to have set or unset? Don't use 1.1.5 unless you are developing. There are several incomplete areas. Use 0.9.9.1. If 0.9.9.1 behaves the same way, let me know.. I have not tested with php 5, so that could be related. Regards, Bill
Re: [users] Help with PTR record please.
Sanjay Arora wrote: Using VegaDNS version 0.9.9.1 1.Getting problem with PTR. My ISP has delegated reverse lookup of my IP to me. Here's output from DNSstuff: How I am searching: Asking g.root-servers.net for 162.221.134.203.in-addr.arpa PTR record: g.root-servers.net says to go to tinnie.arin.net. (zone: 203.in-addr.arpa.) Asking tinnie.arin.net. for 162.221.134.203.in-addr.arpa PTR record: tinnie.arin.net [69.25.34.195] says to go to ns1.comeconnect.com. (zone: 221.134.203.in-addr.arpa.) Asking ns1.comeconnect.com. for 162.221.134.203.in-addr.arpa PTR record: ns1.comeconnect.com [202.164.32.81] says to go to ns1.transcontinental.co.in. (zone: 162.221.134.203.in-addr.arpa.) Asking ns1.transcontinental.co.in. for 162.221.134.203.in-addr.arpa PTR record: Timed out [at 203.134.221.162]. Trying again. Getting Error: PTR soochak.asr.transcontinental.co.in does not end in .in-addr.arpa. on entering the values given below in Add Record (my IP addy is 203.134.221.162): Try this patch to records.php: http://shupp.org/patches/ptr.patch Also, 2.Getting error on editing domain: Notice: Undefined offset: 1 in /home.www/html/vegadns/src/functions.php on line 298 Try adding this to the top of your main index.php: error_reporting(E_NOTICE); The idea is to not send warnings to the screen. Regards, Bill
Re: [users] Group Admins don't have access to domains
Ryan White wrote: I have a user [EMAIL PROTECTED] who is a group admin. He has added a number of domains and now wants to have another group admin also have access to these domains. I created [EMAIL PROTECTED] and in the group owner field put [EMAIL PROTECTED] When user bar logs in he can not see any of the already created domains that are owned by [EMAIL PROTECTED] Is there something that I am doing wrong or are the permissions not complete in ver 0.9.9.1? Each group can only have one admin, I believe. This is completely redone in the 1.1 series, though. It has a much more robust permissions system. However, 1.1 is not ready for prime time yet, and there is not yet a conversion script for migrating. Hopefully within the next month or 2 I'll get it out the door. Regards, Bill
Re: [users] domain templates / default records .... some ideas (again)
[EMAIL PROTECTED] wrote: Hello Bill, Just something I wondered, regarding the template hostnames, or default records for domains.. I mentionend in the past the abbility to be abble to define different templates and let the site admin choose what template to apply asn default to a domain. Another (simple?) abbility would maybe be to let the group-owner (or even the domain-owner ?) the abbility to add some admin/group-owner-defined templates available for the domain. Exemple for some random domain.ext : 1st template let's call it round robin web: ADOMAIN10.0.0.10 ADOMAIN10.0.0.11 CNAMEwww.DOMAINDOMAIN 2nd template, let's call it round robin pop3 and smtp: Apop3.DOMAIN 10.0.0.20 CNAME smtp.DOMAINpop3.DOMAIN 3rd template, let's call it round robin imap and smtp: A imap.DOMAIN 10.0.0.22 CNAME smtp.DOMAINimap.DOMAIN 4th template, let's call it client X dedicated server all ADOMAIN10.0.0.30 CNAMEwww.DOMAINDOMAIN CNAMEpop3.DOMAIN DOMAIN CNAMEsmtp.DOMAIN DOMAIN The user/group/admin user could select to user template 1 3 based on the services providen for that domain.. I'm sure you can figure the comination uses for such system.. Also note that some template cannot co-exist, the user cannot select 4th 1st, 2nd or 3rd templates.. Hope the thought worths something... Sure, I'm not opposed to multiple default record templates. Regards, Bill
Re: [users] question and request feature
Andrea Riela wrote: Hi folks, first, a question: why the NS record uses '', like BIND, and not '.' ? . is really just a shortcut to add an NS, A, ans SOA record in one shot. I always found it confusing to add multiple . records, when you only need one SOA record. Also, when you do axfr-get imports, it uses the individual records, I believe. second, a request for feature: normally we could use the update-data.sh manually or with crontab. What about a web button to apply changes? That would require a setuid cgi or the like to execute it as a user outside the web server. I'm considering a vegadnsd program to handle such tasts, as well as other server administration tasks (binding to IPs, restarting the server, getting info about uptime, etc...) Regards, Bill
Re: [users] about local tag
Andrea Riela wrote: Hi folks, what about local tag? I need to create a conf like that: %in:192.168.17 %ex .17.168.192.in-addr.arpa:192.168.17.x:a: .domain.dom:192.168.17.11:dns.nesys.it:86400::in .domain.dom:81.174.x.x:dns.nesys.it:86400::ex locations are not yet supported in vegadns. Regards, Bill
Re: [users] Report Errors from dnsreport.com
Jeff Montgomey wrote: Probably help if I include my records: #cpsi-mis.com +mail.cpsi-mis.com:68.17.65.212:3600 +ns-atl-b.cpsi-mis.com:68.17.65.220:3600 @cpsi-mis.com::mail.cpsi-mis.com:0:3600 cpsi-mis.com::ns-atl-b:3600 Zcpsi-mis.com:68.17.65.220:domainadmin.cpsi-mis.com::16384:2048:1048576:2560:86400 You're missing an a record for ns-mob-b.cpsinet.com. Try adding: +ns-mob-b.cpsi-mis.com:70.158.1.69:3600 Regards, Bill
Re: [users] trouble with install
Bob Ababurko wrote: Hello- I am finally getting around to configuring this box and I have run up to an error for which I do not find any posts about in the vegadns archives. The error goes like this when I try to log into/run the gui. I shouldn't say log in since there is no logging in.: Fatal error: Call to undefined function: session_name() in /home/vegadns/index.php on line 93 Sounds like your PHP install does not have session support. I am trying to run this on FreeBSD 5.4. Has anyone dealt with this before? Any help would be appreciated. Configure PHP to use sessions. Regards, Bill
Re: [users] PTR Record
Umar Draz wrote: Dear thanks for your mail i follow your instruction but result is same Hostname 252.1.168.192.in-addr.arpa Type PTR Address umarhelp.net Distance (MX only)0 TTL 3600 PTR 252.1.168.192.in-addr.arpa.umarhelp.net does not end in .in-addr.arpa. what i can to do? Make sure there is a trailing dot on the hostname. I don't recall if it will cause this particular error or not, though. I'd have to look at the code. Regards, Bill
Re: [users] Feature Request - Integration API
dopry wrote: Bill, I'm not sure if this fits on your long term roadmap, but a little code reorg to make an API for VegaDNS would be nice. Something to make it easier to add new interfaces to the database like XML-RPC, SOAP or maybe even a libvegadns for c. Sure, I'm open to suggestions. If you check out 1.1.4, you'll see I'm moving all permissions related stuff into the permissions class, which is a step in that direction. Regards, Bill
Re: [users] VegaDNS on Separate Server
Jason Smith wrote: We're getting ready to deploy two tinydns servers and I would like to run VegaDNS on a third, separate web server w/safe_mode enabled. Since the web server runs a control panel that uses bind, I can't install tinydns on that server and I'd like to make VegaDNS just generate [and/or compile] the data/data.cdb file for retrieval by the name servers. My idea was to write a quick PHP script that got all the records from the VegaDNS database and serve up a text/plain data file that I could wget and make on the individual name servers. Any comments/suggestions/advice? The simplest way is to first add the client tinydns servers' IPs to $trusted_hosts in config.php on the VegaDNS server. Then, update the VEGADNS variable in update-data.sh on both client machines to point to the VegaDNS server. Regards, Bill
Re: [users] Update Data Script
Chris Odell wrote: For some odd reason my update-data script will not get new data when run from cron. If I run it from the command line everything works well - Any ideas? Your environment is probably not getting set. Try setting your path at towards the the top like so: export PATH=$PATH:/bin:/usr/bin:/usr/local/bin:/sbin/usr/sbin:/usr/local/sbin (all on one line) Regards, Bill
Re: [users] Re: grabbing info from data file
Neil wrote: Jason S writes: I had absolutely no trouble just setting up axfrdns and using the 'Import Domains via AXFR' tool in vegadns. It was very minimal work. Here's an explanation of the data file format: http://cr.yp.to/djbdns/tinydns-data.html Hi Jason, Axfrdns is now working. I was able to import the dns entries. However, I have a question regarding a record that was imported. Earlier, when I created this MX, I didn't see any trailing dot. BEFORE in vega: mail.nonexistent.com AFTER import in vega: mail.nonexistent.com. Now, I imported it via vega and it has a trailing dot now. Are there any issues with it? I remember back in my BIND days when I create SOA. There should be a trailing dot. However, what I'm showing is an MX record. The trailing dot also happened to the NS record after it was imported. Thanks, Any fully qualified domain name SHOULD have a trailing dot. Many times they are left off, though. tinydns allows them to be optional in the data file. But it advertises them, which is why axfrdns is advertising them. All VegaDNS does is parse the output from axfr-get. It is not adding the trailing dot. Regards, Bill
Re: [users] Is this intentional?
dopry wrote: the bug is in 1.1.3 as well... According to the website 0.9.9 is the current stable and 1.1.3 is dev, yes/no? Correct. oh yeah another note on website typo: *DEVELOPMEDNT CHANGELOG* Fixed, thanks. It would be nice if you had a bug tracker so some of us mortals could clean up the little things when we have time. Agreed. I'll probably try and get this all moved over to sourceforge soon, definitely during the 1.1 dev series. Do you have any future massive changes in mind? None that I haven't already mentioned. Originally, I wanted the web interface to be a complete admin too... One that could add/remove dns services in addition to managing records, and it could also show the status of the services running. But this would require a management daemon to be run locally as apache would not have rights to edit daemontools services. It's still not out of the question, but it's the least of my priorities. And I suspect most people would prefer to NOT have such functionality in a web interface, only record/domain editing. It seems like it will be pretty complete as a DNS administration tool once you have 1.1.4 out and tested thoroughly. Hopefully! Regards, Bill
Re: [users] Is this intentional?
dopry wrote: On Fri, 2005-04-15 at 08:18 -0700, Bill Shupp wrote: I would prefer not to have the service management available through Vega... I give my end users access to VegaDNS I wouldn't want them to have such control... It would be permissions based. The idea was this: VegaDNS can administer all aspects of DJBDNS. Add/Remove which IPs it listens to, maintain dnscache settings, etc... Of course, this would be permissions based. But the idea was to make djbdns so easy to administer, that it would encourage more people to switch to it. But I certainly have the same reservations about allowing such changes to be done over the web. That's why it has not been a priority, and I'm not sure that it ever will be. An inherent service monitoring tool wouldn't be so bad. I'm already using spong though to monitor servers. Segregating these functions into a companion tool is not a bad idea... Why would you want to add/remove services from a running server, especially production? It would make sense for a general network/server administration tool that allowed you to provision services to servers or re-provision them as needed, but you would probably want to include FTP, HTTP, and email administration if you were working on such a tool. Perhaps. I'm not personally interested in managing all my services from a web interface. However, as the designer of a djbdns web interface, I thought it would be interesting to go the full distance with that application only. It would be nice to have such a tool and an intuitive control panel in the vein of VegaDNS for all of these things. but inter7 I think is already on that ball with vHostAdmin, but I still haven't found an admin tool that does it all well, even on the commercial market. The emulation of SquirrelMail's plugin architecture in vHostAdmin is a smart move, and could prove it a pretty popular tool in the long run. I'm looking forward to seeing how it develops. Regards, Bill
Re: [users] fresh instalation help
Bogdan wrote: Hi, guys I have the following error after a fresh instalation: Warning: mysql_connect(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) in /var/www/html/vegadns/src/connect.php on line 28 error connecting to database if I connect from the comand line with the same/user pass like in config.php it works. thank you. Perhaps PHP is looking to the wrong socket file. Is /var/lib/mysql/mysql.sock the right socket file? If not, I think this is configured in php.ini. Change it there. Regards, Bill
Re: [users] fresh instalation help
Bogdan wrote: the user pass are corect because I tried to connect from cmd line and it works, how can I check if the php can talk with mysql? tnks again. Try connecting to the database test, it doesn't require a user/pass. Bill
Re: [users] fresh instalation help
Bogdan wrote: it works with test Then you have your answer... there's something wrong with your mysql permissions for that user. Regards, Bill
Re: [users] Fatal error: Call to undefined function: session_name() in /usr/local/www/data/vegadns/src/session_start.php on line 28
Jeremy Gray wrote: I just reinstalled VegaDNS from scratch on a new server and I'm getting this error Fatal error: Call to undefined function: session_name() in /usr/local/www/data/vegadns/src/session_start.php on line 28 Any idea what that's about? Sounds like you do not have session support in PHP. Regards, Bill
Re: [users] VegaDNS hangs when creating a new domain...
Jeremy Gray wrote: First time install here... Whe I create a new domain it just hangs. However, if I click log out, then log back in and look at domains the new domain is there. the domain seems to get created. Sounds like there was an error.. check your httpd error logs for more detailed information. Also for some reason it created a file in my tinydns/root directory named: -rw-r--r-- 1 root wheel 0 Mar 29 06:01 data.srv-$[$[0]+1] I'm guessing that the file above should have had those strings replaced by some other value. That file was created by the shell script that dumps the database. Does your cron entry redirect all output to /dev/null? If so, remove that part so that cron can report any errors. I'm guessing these 2 things are related. Regards, Bill
Re: [users] ipv6 reverse problems
Niek wrote: Hi list, I run vegadns 1.1.3 just to administer a ipv6 reverse delegation I got. Vegadns doesn't seem to like ip6.arpa only in-addr.arpa: I add the domain: 5.9.3.0.8.3.8.0.1.0.0.2.ip6.arpa Then I create a ptr: test - 2001:838:395::1 PTR 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.9.3.0.8.3.8.0.1.0.0.2.ip6.arpa does not end in .in-addr.arpa. Please note that I'm only going to run the ip6.arpa, I'm not looking to do . (i.e. all domain data that point 's to my ipv6 space, are running on other servers). I have had one other report of this.. It will be a day or so before I have time to look over that code, as I'm finishing up the new permissions code right now. If anyone else happens to get to it before me, please feel free to submit a patch. Regards, Bill
Re: [users] accounts pagination
Bob Hutchinson wrote: Here is a patch that adds pagination to accounts. It affects src/users.php and templates/show_users.tpl It was made using vegadns-1.1.3, and is based on the code from domains.php I hope it works for you got it, I'll test it out soon. Thanks, Bill
Re: [users] small bug in records.php
Bob Hutchinson wrote: A small bug appeared in vegadns-1.1.2/src/records.php It only showed because I'm running E_ALL in php.ini It only affects the 'success' message after adding a record Attached is the diff It's mentioned in the 1.1.2 changelog, but didn't actually get added until 1.1.3. So it's already fixed. Thanks, Bill
Re: [users] list domains - alphabet out of order.
Michael wrote: Bill Shupp wrote: Michael wrote: Just noticed the alphabet is out of order while listing domains for VegaDNS: Q | R | S | T | U | V | X | Y | W | Z Got it, fixed in 1.1.4. Thanks! Bill Not sure if you want to fix the screen shot to: http://www.vegadns.org/images/screenshots/domains.jpg Nah, they will get replaced when the 1.2 series is released. Regards, Bill
Re: [users] Possible security flaw for some people
Michael wrote:
For a group_admin account, you don't have access to view accounts
unless you are the group owner, but, you can go to Edit My Account, then
change the cid= option to display any info for any cid.
This may be undesirable and qualify as a security risk for some people.
In 'users.php' maybe check permissions if user_mode == edit_account just
like if user_mode == edit_account_now ???
Michael
diff -ur users.php.orig users.php
--- users.php.origThu Feb 3 19:06:42 2005
+++ users.php Thu Mar 3 18:35:41 2005
@@ -36,6 +36,23 @@
// Get account info
$account_info = get_account_info($id);
+// If group_admin, make sure this account belongs to the user
+if($user_info['Account_Type'] != 'senior_admin'
+ $user_info['cid'] != $account_info['cid']) {
+if($user_info['Account_Type'] == 'group_admin'
+$account_info['gid'] != $user_info['cid']) {
+$message = span class=\error\Error: you do not have permission to edit
this account/span\n;
+header(Location: $base_urlmessage=.urlencode($message));
+exit;
+} else if($user_info['Account_Type'] == 'user'
+$_REQUEST['cid'] != $user_info['cid']) {
+$message = span class=\error\Error: you do not have permission to edit
this account/span\n;
+header(Location: $base_urlmessage=.urlencode($message));
+exit;
+}
+}
+
+
// Set user_mode_next and title
$smarty-assign('user_mode_next', 'edit_account_now');
$smarty-assign('account_title', 'Edit Account');
Got it, thanks!
Bill
Re: [users] PHP issues on vegadns 1.1.1
Derkowski, Matthew wrote:
I get this error when trying to add A records, and some times it adds
two records. I don't really know php so I am not sure where to begin
to diagnose this. I found a few threads that said to set
error_reporting = E_ALL
~E_NOTICE on my php.ini, but that is already set.
*
**
*Notice*: Undefined variable: message in
*/var/www/localhost/htdocs/vegadns-1.1.1/src/records.php* on line *408*
*Warning*: Cannot modify header information - headers already sent by
(output started at
/var/www/localhost/htdocs/vegadns-1.1.1/src/records.php:408) in
*/var/www/localhost/htdocs/vegadns-1.1.1/src/records.php* on line *408*
Try changing these lines:
$smarty-assign('message', Record added successfully!);
header(Location:
$base_urlmode=recordsdomain=.urlencode($domain).message=.urlencode($message));
exit;
To this:
$message = Record added successfully!;
$smarty-assign('message', $message);
header(Location:
$base_urlmode=recordsdomain=.urlencode($domain).message=.urlencode($message));
exit;
Bill
Re: [users] Adding host records for vegadns
Derkowski, Matthew wrote: Is there a way to have host record additions create both A PTR records for tinydns ? (so in the tinydns data file it is a = record not a + record) Possibly a new record type option on the drag down list, for a combined record option. Not yet. It's on the TODO list. Bill
Re: [users] whois addon for vegadns
Bob Hutchinson wrote: On Tuesday 22 Feb 2005 22:40, Bill Shupp wrote: Bob Hutchinson wrote: I would like to suggest a minor improvement to DNS query. If the input is an ip, run dnsname instead of dnsq. Handy for reverse dns checks. I don't have a problem with this. But it's lower on my priority list. If you care to submit a patch, that would be great. here it is. only alters dnsquery.php http://midwales.com/hutch/downloads/vegadns/dnsquery.patch Got it, thanks! I did swap your preg_match() with the validate_ip() function in functions.php, as it's just simpler to use that. Regards, Bill
Re: [users] whois addon for vegadns
Bob Hutchinson wrote: On Wednesday 23 Feb 2005 00:17, Bill Shupp wrote: Bob Hutchinson wrote: On Tuesday 22 Feb 2005 22:40, Bill Shupp wrote: Bob Hutchinson wrote: I would like to suggest a minor improvement to DNS query. If the input is an ip, run dnsname instead of dnsq. Handy for reverse dns checks. I don't have a problem with this. But it's lower on my priority list. If you care to submit a patch, that would be great. here it is. only alters dnsquery.php http://midwales.com/hutch/downloads/vegadns/dnsquery.patch Got it, thanks! I did swap your preg_match() with the validate_ip() function in functions.php, as it's just simpler to use that. Ah yes, I had forgotten that it was there I just posted 1.1.3 on www.vegadns.org that has all these late afternoon changes. I only bothered posting it so that people using the early 1.1x series could get the last bug fixes before I implement permissions changes which are far more pervasive. Regards, Bill
Re: [users] Error: you do not appear to be logged in.
Jason 'XenoPhage' Frisvold wrote: Allen Parker wrote: 4.1.8 (have been even when it worked with 0.9.7) also, haven't changed any mysql settings, and it's funny that the only problem is that it's telling me that i'm not logged in when i log in... after populating a new domain by hand (mysql query browser ssh tunnel = joy) the update-data.sh worked flawlessly. Damn.. I was gonna suggest that the new password hashing in 4.1.x was causing the problem, but since you were running 0.9.7 with it, then I can't really suggest that anymore.. :( Hmmupdate_data.sh would work as it doesn't require a login ... It's only getting the data from the mysql database and reporting it back ... I can't help but think that this may still be a mysql password problem ... Does the sessions directory have the right permissions? It sounds like verify_session() is what is failing. vegadns/sessions must be read/writable by the web server user. Regards, Bill
Re: [users] VegaDNS 1.1.0 - development branch
Rodrigo Borges Pereira wrote: Hi Bill, Found some glitches when importing domains. Here's my code modifications: I don't quite follow the diff. Can you do a diff -u, and attach it, or maybe post it? That will make it easier to read as well. Thanks! Bill
Re: [users] VegaDNS 1.1.0 - development branch
Rodrigo Borges Pereira wrote: and display_errors = On :p It is. And I got the ones you reported previously. Just not this last patch. Regards, Bill
[users] VegaDNS 0.9.9 Released
All, I have posted VegaDNS 0.9.9 today. Major features include: - Bug fixes for wild card support, default records, sanity checks, and authenticate_user() - Smarty update (READ UPGRADE!) As stated above, please read UPGRADE if you are upgrading. Unless there are any other bugs found, I'll be renaming this 1.0 next week. Also next week I will be releasing a 1.1 development branch. This branch will involve some major changes in the permissions system to allow for more robust delegation, a database abstraction layer, more logging, better PTR record delegation, as well as the SRV and IPv6 patches recently submitted to the list. Regards, Bill Shupp
Re: [users] question about and ns records.. and wildcards
Brian wrote: I have a tinydns server that I am trying to port/put into vegadns; to make life easier on the people here. in the original tinydns data file (that was created by hand/a human) I have this: Zdomain.name:192.168.1.248:hostmaster.domain.name::7200:3601:86400:3601:43200:: domain.name:192.168.1.248:500 it seems that vegadns will not allow me to make this same entry (regarding the entry) I cannot put an IP address in there this is the closest thing I can get: Zdomain.name:192.168.1.248:hostmaster.domain.name::16384:2048:1048576:2560:86400 domain.name::ns.domain.name:3600 +ns.domain.name:192.168.1.248:3600 Is there something syntactily incorrect about my entry with an IP? also is there no way to do a wildcard entry? *.something.domain.name as an A record isn't accepted. How can I get that to be entered? Thanks in advance. An NS record should not point to an IP, I believe. You need it to point to a hostname, and then have an A record for that hostname. Regards, Bill
Re: [users] question about and ns records.. and wildcards
Brian wrote: Ok.. (like you didn't know this was coming.. ) Where would I find out how to do it? hostname *.blah.domain.name type A address 192.168.1.200 gives this error: *.blah.domain.name. is not a valid A record name when I use \*.blah.domain.name I get this error: \\*.blah.domain.name. is not a valid A record name the tinydns-data page looks like it's an A record. where would I be able to find that information on how to add a wildcard entry? I didn't see anything in the archives. Thanks in advance I just tried with 0.9.7, the only version I have installed right now.. and it works. The sanity checking in 0.9.8 may have broken wildcards. I'll have to look into that later today. Regards, Bill
Re: [users] Hook request
Ron Guerin wrote: I'd submit a patch but I'm under the impression I haven't made the case for it being worth accepting. The more I think about this, the more it seems like it might not be a bad idea for very large sites. However, it should be an option set in config.php. Can you easily alter it to work that way? Regards, Bill
Re: [users] no record log ??
Sebastien Guilbaud wrote: I wonder whether I've missed something or not : it seems to have a log of domain-based operations (add remove, axfr and so on), but no log of record-based operations (removal of a record for instance) ? have a nice day ! I don't think you missed anything. Logging is incomplete, and I have not had time to work on that. It'll be improved in the next development release. Is there any help needed, patches ? Sure, patches are always welcome! Bill
Re: [users] Setting up domain name servers
Paul Swainson wrote: You have almost answered it at the end, what I was getting at was setting up a secondary name server on a second machine for fault tolerance. So if I add a second ns record on the primary sever to my domain this time containing the domain name for the secondary name server (tiny_dns IP on the secondary nameserver, not the ext_dnscache IP) this will complete internal domain name ns record setup. Now, copy (rsync or a suggested method?) the all tiny_dns data and vegadns data to the secondary name server. If the client machines on my network have the 2 name servers ext_dnscache IPs in there network settings, the primary is queried first, if this had been powered off or unable to answer queries for some reason, the client machine the queries the secondary name server, this has the 2 ns records, the first NS record is dead so I then assume it moves to the second NS record which contains the hostname (IP) for the secondary name server resulting in the query being answered? I'm sorry this is long winded but I need to understand each stage of admin and mechanics. You may have a easier way of explaining this for which I would be eternally grateful The idea of having 2 authoritative servers, and one cache is a good plan. I'm not sure if I follow what you mean by If the client machines on my network have the 2 name servers ext_dnscache IPs in there network settings... but this is what I think you should do: Have all your local host information in NS1. Use rsync (automated) to sync the data to NS2. Have an external cache that does lookups to the outside world but also has direct routes for your internal domain pointing to NS1 and NS2. This way, all your clients are pointed to the external cache *only*. And when they lookup a local hostname, the cache gets the information from NS1 or NS2 (I believe the choice is random, and if one is down the other is tried before giving up). That should provide the fault tolerance you want, and provide local data information as well. If you are worried about having only one cache, setup a second identical to the first, and put both IPs in the client machines for lookups. Regards, Bill
Re: [users] GUI improvement ideas
[EMAIL PROTECTED] wrote: Hello, I'm really glad to know 1.0 will soon be out soon, and i thought i should write about a few GUI improvement ideas i had while using vegadns since a year now. Keep in mind i know most of these will feel somehow useless to power-users. Most settings resulting from changes i'm suggesting could be edited once and for all from config.php.. Here they are: . The abbility to allow or not, all users to change default TTL, SERIAL, etc for their domains (I had the case where people would set TTL of 1MS hopping that would improve dns resolving .) Perhaps there could be separate limits on Users and Group Admins via the config file. Senior Admins should not be limited. . I saw logs save pretty much everything, I was wondering if on the add domain form, we couldn't specify for how long the domain was registered.. Therefore we could have (based on the date the domain was added), an exact idea of when the domain should expire.. How many times do we have to deal with people that don't receive warning from their registrar (cause for exemple they changed email..) and wonder why, oh why is this domain not working.. (of course we do take the abbit of doing a whois first.. but not all clients know what a whois is ..) Hmm, I see your point. But this still seems arbitrary to me. I guess you could have a display for the domain's date creation (the logs will keep time stamps, so that could be done easily), and then you'd know when it was created in *this* database, but not necessarily when it was registered. You could also manually enter the registration expiration, but that would require manual updating when it was renewed, etc. I just don't see an efficient way to store this information. I wonder how feasible it would be to add hook to whois, and parse out the expiration date. Is there any standard for registrars to display this info, or would it be text parsing? . I (only) have around 35 domains in the db, and i must say, clicking domains to only reach a domain starting with letter Z sounds a bit too much.. I was just wondering if the alphabetical index, couldn't be displayed on the startup page directly, rather than having to click domains first, to than see the full listing and alphabetical sorting options.. (or some option like the $per_page, but in this case would become $per_domain to select how many domains to display per page, thus lowering the time needed to access the alphabetical sorting options..) Maybe a better solution is to just do away with main menu. Since all menu options are available at the top at all times, why not make main menu be the domain listing? . The abbility to sort domains per domain extentions. This should not be hard to add, although I've never personally needed it. Anyone else have an opinion on it? .The abbility to let users add or not subdomain or new domains. I had a case where a someone tryed to add as many domains as he could.. just for .. fun.. Therefore being abble to just disable adding domains.. could help in some setups. My approach to this is to leave them inactive, so a senior admin *must* activate any domains created by users or group admins. I think this is sufficient. If you have a user playing with the dns software for fun, they should probably not a user anymore. That's all for now, maybe more will pop in my mind.. Thanks for the feedback. Regards, Bill
Re: [users] VegaDNS 0.9.8
Bob Hutchinson wrote: On Wednesday 08 December 2004 22:17, Bill Shupp wrote: All, I have posted VegaDNS 0.9.8 to http://vegadns.org. This will likely be the last release before 1.0, unless anyone finds any problems. Please help test if you have time. Installed it and it all looks OK, it lets me enter an ip where I should enter a domain, but why would I want to do that anyway? I don't think an IP address is illegal (I didn't bother to check). The trick is to get a cache to find it. ;) Bill
Re: [users] update-data.sh not functioning correctly...
Paul Maric wrote: I installed TinyDNS and had it operational and then decided to give VegaDNS a shot, it installed fine, but when I ran update-data.sh it said it completed the command, but it simply added another file to the TinyDNS folder and didnt update the data file correctly and just removed all the data inside it. Can anyone recommend what the problem could be? And how to fix it? How did the data that got removed from the file get there in the first place? Was update-data.sh working before, then suddenly stopped working? If so, what changed? Regards, Bill
Re: [users] Default Domans MX Distance
Bob Hutchinson wrote:
On 23/08/04 15:40, Ryan White wrote:
I just got a report from a user to this effect:
I Added a MX record in the default domains. MX Record has distance 300
(looks fine in default domain manager)
When a new domain is added the default MX record has a distance of 0.
Although this works it's not the desired effect.
I reported this bug to this mailing list on 14/07/2004
here is the diff for my way of solving it:
here is a diff
--- /var/vegadns-0.8.1/src/domains.php Fri Jun 18 04:45:48 2004
+++ /var/www/vegadns-0.8.1/src/domains.php Wed Jul 14 10:34:13 2004
@@ -257,11 +257,12 @@
while(list($key,$row) = each($records_array)) {
$host = ereg_replace(DOMAIN, $domain, $row['host']);
$val = ereg_replace(DOMAIN, $domain, $row['val']);
-$q = insert into records (domain_id,host,type,val,ttl)
+$q = insert into records (domain_id,host,type,val,distance,ttl)
values('$id',
'.mysql_escape_string($host).',
'.$row['type'].',
'$val',
+'.$row['distance'].',
'.$row['ttl'].');
mysql_query($q) or die(mysql_error());
dns_log($id, added .$row['type']. $host with value $val);
hope this helps...
(I tried upgrading to ver 8.1 but this did not solve the problem.)
I think this patch should fix it but maybe not all records need the
distance copied across?
--- vegadns-0.8.1/src/domains.php Thu Jun 17 20:45:48 2004
+++ /vegadns-0.8.1-p/src/domains.php Mon Aug 23 07:25:11 2004
@@ -257,11 +257,12 @@
while(list($key,$row) = each($records_array)) {
$host = ereg_replace(DOMAIN, $domain, $row['host']);
$val = ereg_replace(DOMAIN, $domain, $row['val']);
-$q = insert into records (domain_id,host,type,val,ttl)
+$q = insert into records
(domain_id,host,type,val,distance,ttl)
values('$id',
'.mysql_escape_string($host).',
'.$row['type'].',
'$val',
+ '.$row['distance'].',
'.$row['ttl'].');
mysql_query($q) or die(mysql_error());
dns_log($id, added .$row['type']. $host with value $val);
This is already fixed in 0.9, which I have not yet posted. I'll get it
posted as soon as possible.
Regards,
Bill
Re: [users] VegaDNS for Slaves?
Eric Harris wrote: Howdy, Is it possible to use VegaDNS to manage slaves? Works great for my masters, but I'd like an easy way to manage laves on y tinydns server. What would you need to manage on a slave server? The idea of a slave is that it gets its data from a master server. i.e., there's no local data to manage. Regards, Bill
Re: [users] Default Records Question
Brian wrote: Hello all, I'm trying to setup the default records for things and I'm wondering this can be done. I'm trying to pre-establish MX records to a specified mta. I see that the primary nameserver can be whatever I want, but when I put in a 'default' MX it prepends '.DOMAIN' on to it; even if I put a.mx.blah.com. it will show up as a.mx.blah.com..DOMAIN. Is this desired? Is there someway to change that? I think you might be going about it the wrong way. I can do this properly. Let's say you want all new domains to have the MX record of mail.merchbox.com. To set this up in the default records, in the add record screen, the hostname is DOMAIN, and the address is mail.merchbox.com. This way a new domain called testmx.com will get an MX record of mail.merchbox.com. Make sense? Regards, Bill Shupp
Re: [users] bugfix
bob wrote:
I have found what appears to be a bug.
It's in the distance field of an mx record, if I create two records in
the default_records table, the distance field is set in the db as
I filled it in, with 10 and 20 for the distance.
However when I create a record based on these defaults, the distance field
is set to 0 for both.
If I edit those two records manually and set the distance to 10 and 20,
and then export them to the tinydns data file, they appear OK
So the bug lies somewhere in the code that creates a new record based on
the settings in default_records.
I have found it, in domains.php, line 265
here is a diff
--- /var/vegadns-0.8.1/src/domains.php Fri Jun 18 04:45:48 2004
+++ /var/www/vegadns-0.8.1/src/domains.php Wed Jul 14 10:34:13 2004
@@ -257,11 +257,12 @@
while(list($key,$row) = each($records_array)) {
$host = ereg_replace(DOMAIN, $domain, $row['host']);
$val = ereg_replace(DOMAIN, $domain, $row['val']);
-$q = insert into records (domain_id,host,type,val,ttl)
+$q = insert into records (domain_id,host,type,val,distance,ttl)
values('$id',
'.mysql_escape_string($host).',
'.$row['type'].',
'$val',
+'.$row['distance'].',
'.$row['ttl'].');
mysql_query($q) or die(mysql_error());
dns_log($id, added .$row['type']. $host with value $val);
works now
vegadns is nice, I would personally prefer to use . and = type records, but it
does appear to be producing good dns records, at least on my devbox ;-)
I suspect that using Z and type records might interact better with bind/
named, but I don't really know and can't test that thesis easily.
Hope this helps
Thanks! I'll get this added to 0.9.
Regards,
Bill
Re: [users] Successful 0.8.1 upgrade
Jason 'XenoPhage' Frisvold wrote: Hi all, I've successfully upgraded to 0.8.1 from 0.7.0 ... Worked out flawlessly.. :) Great to hear. I spent a bit of time on the upgrade script and document, so it's good to hear it working in the field. I have a question regarding the creation of new records. Which records need to end in a . ?? It looks like NS, CNAME, and PTR records require this.. Would it be possible to put in some sort of check to ensure that there is a trailing . ?? A dot should always come after the TLD, i.e. com.. However, I believe they are optional in djbdns. Thought I can't seem to put my finger on that in the website right now. Also, the ability to sort by the different fields would be nice... That should be easy to add, and useful for large zones. I'll look into it. Regards, Bill
[users] 0.8 Released
All, I have released VegaDNS 0.8. The major improvements include: - Make sure PTR records are within the appropriate zone (to avoid duplicates, insure proper zone info) - Added ability to edit records - Added view logs (needs work) - Switched from clear text to md5 passwords (see UPGRADE!!) If you are upgrading from an earlier version, make sure you read UPGRADE, as you will need to alter your accounts table structure before logins will work. There's an easy script to use, so don't fear... just read the UPGRADE file. As always, please report any problems or bugs to the users list or to me directly. Cheers, Bill Shupp
Re: [users] Sending mail to admin on new domain.
Ryan White wrote: I was reading through domains.php and noticed this: Line 271: // Email the support address if an inactive domain is added $body = inactive domain \$domain\ added by .$user_info['Email'].\n\n; $body .= \n\nThanks,\n\n; $body .= VegaDNS; mail(strtolower($_REQUEST['username']),New Inactive Domain Created,$body , Return-path: $supportemail\r\nFrom: \$supportname\ $supportemail); From what I can tell I have never gotten an email when I create new domains. Then again I am the super-admin. From what I can gather it is sending the email to the user that added the domain. What would be awesome is if the super-admin was notified that this domain was created. Then we don't have to randomly guess when we need to activate inactive domains ;). I could be mistaken on what this little bit of code is supposed to do... -Ryan Domains created by a senior admin are automatically active. So no email is necessary. Regards, Bill
[users] Alias Domains
A colleague of mine suggested adding alias domains in VegaDNS. An Alias domain would simply contain identical records for as the domain it is aliased to. This could be accomplished fairly easily either by adding a couple of columns to the domains table, such as type and real_domain, or perhaps a new table called alias_domains. Either way, the data file would be built with the records duplicated, rather than using CNAME records. First off, how many people would find this useful? Secondly, does anyone have a more elegant idea of how to implement it? Regards, Bill Shupp
