Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: zaker on April 29, 2004, 02:52:43 AM
-
Has anyone tried this how-to http://www.sglinuxos.org/modules.php?name=Content&pa=showpage&pid=3
And if so, does anyone know if it will work on SME 6.01? it says for 5.5 & 5.6.
thanks
tom
-
I have not tried it, but I did drop them an email, and they did reply. They said they were working on a verison for 6.0 > , but it was not ready yet. This was about 6 weeks ago, and I have heard nothing more
Bob
-
I think it is actually a lot easier than everyone is making it.
There's an e-smith entry in /home/e-smith/configuration for tinydns
You can simply run
shell$ /sbin/e-smith/db setprop tinydns ListenIP xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP you want it to listen on.
Then
shell$ /sbin/e-smith/expand-template /var/service/tinydns/env/IP
shell$ /etc/rc.d/init.d/tinydns restart
I have found a reboot is in order next if things are sluggish. I'm not sure why this is. You can always unset the property if this doesn't work for you.
I have not tested this on a 'live' server yet. The difference in the "dig @IP domain" output is as follows...
bash-2.05a$ dig @192.168.1.250 allegrodance.ca
; <<>> DiG 9.2.1 <<>> @192.168.1.250 allegrodance.ca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30262
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;allegrodance.ca. IN A
;; ANSWER SECTION:
allegrodance.ca. 86400 IN A 192.168.1.250
;; Query time: 4 msec
;; SERVER: 192.168.1.250#53(192.168.1.250)
;; WHEN: Sun Jun 20 17:29:32 2004
;; MSG SIZE rcvd: 49
****Then after I changed the listen IP
bash-2.05a$ dig @192.168.1.250 allegrodance.ca
; <<>> DiG 9.2.1 <<>> @192.168.1.250 allegrodance.ca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17947
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;allegrodance.ca. IN A
;; ANSWER SECTION:
allegrodance.ca. 86400 IN A 192.168.1.250
;; AUTHORITY SECTION:
allegrodance.ca. 259200 IN NS totoro.e-xyn.com.
;; ADDITIONAL SECTION:
totoro.e-xyn.com. 86400 IN A 192.168.1.250
;; Query time: 122 msec
;; SERVER: 192.168.1.250#53(192.168.1.250)
;; WHEN: Sun Jun 20 17:41:28 2004
;; MSG SIZE rcvd: 95
As you can see the AUTHORITY and ADDITIONAL are both set to 1 afterwards.
If anyone tests this and finds it to be working on a 'live' or 'staging' server please let us all know.
Thanks,
Jeremy
jeremy@e-xyn.com
-
The line
/sbin/e-smith/db setprop tinydns ListenIP xxx.xxx.xxx.xxx
should read
/sbin/e-smith/db configuration setprop tinydns ListenIP xxx.xxx.xxx.xxx
Sorry, I left out the configuration parameter.
-
Alright everyone or anyone who is interested. I successfully made a stock e-smith server 6.x have external DNS using the tinydns that is already installed.
It is a long process but would only take someone about 15 minutes to accomplish with a howto.
I have it so that it publishes domains internally and externally automatically and updates the external IP if that ever changes AND it's template based in the custom templates with the exception of one web action I had to edit but I may template that later.
Anyhow if anyone is EXTREMELY interested in this I can put together a howto as I wrote my process down for once in my life. Just reply to this post or email me with requests for this. If no one bothers I won't either.
Jeremy
jeremy@e-xyn.com
-
Jeremy
That HOWTO would be very interesting, please go ahead and create it.
Thanks
-
Yes, over here. Wanna read. Please do.
-
I will try and the howto together in the next couple of days make sure I check all the paths and all that to be sure it accurate. Keep checking back. Hopefully the nice people here will grab it and put it in the howto section as well since the one link to public DNS there seems broken.
-
I will try and put the howto together in the next couple of days make sure I check all the paths and all that to be sure it accurate. Keep checking back. Hopefully the nice people here will grab it and put it in the howto section as well since the one link to public DNS there seems broken.
-
Jeremy -- Thank You -- Very much interested and waiting patiently
-
As always there is no warranty and I take no responsiblity for damages or lost files that the information
contained in this document might cause you. Everything here worked for me but you are still to use
this at your own risk and test it on a staging server before trying it on your live server.
A few notes:
1. DNS seems to always be a confusing issue: or at least it always is for me. It took me weeks to figure out
BIND in e-smith 4.1.2 and it took me a few days to iron this one out with the knowledge gained from that.
2. This tutorial will allow you to add/delete domains using the server-manager and make them accessible to the
public without interfering with the internal DNS. That being said, ALL domains you have listed will be
accessible to the outside world. If you want an intranet make those domains accessible to the local network
only in the ibay settings. This tutorial will also allow the server to update all external DNS entries as well
as the listening IP that queries are accepted on automatically.
3. For security reasons (and I would imagine to save CPU/bandwidth) tinydns will not answer ANY external queries
it does not have a DNS entry for. This cannot be changed so you will not be able to make this a completely
public DNS in that respect. The server WILL still resolve ALL domains from within the internal network as
usual.
4. To have a truly public DNS server (to be able to register domains to use your server as a Name Server) you
will need to register it as such and you MUST have a static IP to do this. I cannot help you with this.
If you want to do this you will have to look up more information on the internet. I do know that this is
free to do it just takes some time and effort.
5. ONTO THE HOWTO!!!
Here are the steps involved
1. Open UDP port 53 for incoming requests using iptables
2. Create two user account for the external dns to use and keep them locked
3. Create a new tinydns service called something like tinydsext (so you know it's external DNS)
4. Add an e-smith event file to update the external DNS whenever the external IP changes
Seems simple doesn't it.
1. Open UDP Port 53 for incoming requests using iptables
Update iptables starting script to allow incoming packets to port 53.
mkdir /etc/e-smith/templates-custom/etc/rc.d/init.d/masq
create a file there called 45AllowPUBDNS
# begin file
{
my $status=$tinydsext{status} || 'disabled'
$OUT = allow_udp_in(53,
($status eq 'enabled'));
}
#end file
Then you need to expand the template
/sbin/e-smith/expand-template /etc/rc.d/init.d/masq
and restart masq to apply the new rule
/etc/rc.d/init.d/masq restart
You should see:
Shutting down IP masquerade and firewall rules: Done!
Enabling IP masquerading: done
If you see a bunch of errors check to make sure everything in 45AllowPUBDNS is exactly as it is shown here.
That part is done!
2. Create two user accounts for the public dns to use.
This is directly from the the tinydns configuration pages.
Create two users. I named mine 'tinydnsext' and 'dsnlogext'. You need one to run the service and one to run
the logs as I understand it. Create these users using the e-smith server-manager user panel.
Leave the accounts locked (don't reset the password - we don't need them).
Part 2 is done!
3. Create a new tinydns service called something like tinydsext (so you know it's external DNS)
This will create a whole new tinydns service called tinydnsext in the /var/service dir. I put it there because
that is where the e-smith internal tinydns is. The IP at the end here can be anything but 127.0.0.1 and it is just
a place holder until we get the templates set up to change it. It is the listening IP for the new DNS service.
If you know your external IP you can put it in there.
tinydns-conf tinydnsext dnslogext /var/service/tinydnsext 192.168.10.10
Now you need to edit /home/e-smith/configuration and add this line:
tinydnsext=service|status|enabled
If you ever want to shut off the external dns you simply run
/sbin/e-smith/db configuration tinydsnext setprop status disabled
/sbin/e-smith/expand-template /var/service/tinydsext/env/IP
/etc/rc.d/init.d/tinydsnext restart
or you can just stop tinydnsext service but it will start again upon reboot
Now you need to make all the tmeplate files for the tinydnsext
Create the directory /etc/e-smith/templates-custom/var/service/tinydsnext
copy all the files from /etc/e-smith/templates/var/service/tinydns to the custom directory above
cd /etc/e-smith/templates-custom/var/service/tinydnsext/env
pico IP
You should see this
{
my $ip = $tinydns{'ListenIP'} || "127.0.0.1";
"$ip";
}
change it to look like this
{
my $ip = $ExternalIP;
"$ip";
}
and save your changes
cd ../root/data
delete the file 70genericHostARecords - we don't need it.
delete the entire 'sub get_generic_hostentries' function from 00functions
replace the occurance of '$LocalIP' with '$ExternalIP'
and '$LocalNetmask' with '$ExternalNetmask'
and '127.0.0.1' with '$ExternalIP'
in 30NameServers, 50DomainARecords
expand the templates
/sbin/e-smith/expand-template /var/service/tinydnsext/env/IP
/sbin/e-smith/expand-template /var/service/tinydnsext/root/data
compile the data into tinydns format
make sure you cd to the proper directory
cd /var/service/tinydnsext/root
/usr/local/bin/tinydns-data
restart the service - you need one more symbolic for this
ln -s daemontools /etc/rc.d/init.d/tinydnsext
/etc/rc.d/init.d/tinydnsext restart
Create a file /etc/e-smith/events/actions/update-dnsext
# begin file
#!/usr/bin/perl -w
#----------------------------------------------------------------------
# copyright (C) 2002 Mitel Networks Corporation
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
#
# Technical support for this program is available from Mitel Networks
# Please visit our web site www.mitel.com/sme/ for details.
#----------------------------------------------------------------------
package esmith;
use strict;
use Errno;
use esmith::templates;
#------------------------------------------------------------
# Configure djbdns's tinydns DNS server
#------------------------------------------------------------
#set the ListenIP to external IP
esmith::templates::processTemplate ({
TEMPLATE_PATH => "/var/service/tinydnsext/env/IP",
PERMS => 0644,
});
#apply the new external IP to the data file for external zones
esmith::templates::processTemplate
( {
TEMPLATE_PATH => "/var/service/tinydnsext/root/data",
} );
chdir "/var/service/tinydnsext/root"
or warn "Failed to change working directory";
system("/usr/local/bin/tinydns-data") == 0
or warn("Failed to update tinydns external zone data.\n");
exit (0);
#end file
This will automatically update the external DNS ListeningIP and all the records to point to the right IP
whenever a new domain is added or the external IP changes
Create three symbolic links to this file
ln -s ../actions/update-dnsext /etc/e-smith/events/ip-change/S86update-dnsext
ln -s ../actions/update-dnsext /etc/e-smith/events/domain-create/S51update-dnsext
ln -s ../actions/update-dnsext /etc/e-smith/events/domain-delete/S51update-dnsext
The last will refresh the domain listings omitting the domain you just removed.
These all apply to the server-manager processes.
That's IT!!! I apologize if anything has been left out. Please email me at jeremy@e-xyn.com if you have
any concerns, questions or additions I should know about this tutorial.
-
you must set tinydnsext up as a service by issuing the command
ln -s /var/service/tinydnsext /service/tinydnsext
This will keep it running no matter what
-
Superb Jeremy - Thanks! :lol:
I wonder iof any nice people have thought about a panel for this?
-
I don't really see a need to make a panel for this. As described in the HOWTO everything I did integrates seamlessly in to the Domain panel as well as an ip-change in the system configuration.
I was thinking of making a panel that would handle hosting DNS entries that weren't on the server. That would require it's own panel.
Jeremy
-
Can you look this over and tell my why this is failing? Thanks
-rw-r--r-- 1 root root 98 Jun 29 10:03 45AllowPUBDNS
[root@linux1 masq]# cat 45AllowPUBDNS
{
my $status=$tinydsext{status} || 'disabled'
$OUT = allow_udp_in(53,
($status eq 'enabled'));
}
[root@linux1 masq]# /sbin/e-smith/expand-template /etc/rc.d/init.d/masq
WARNING in /etc/e-smith/templates-custom//etc/rc.d/init.d/masq/45AllowPUBDNS: Sc
alar found where operator expected at /etc/e-smith/templates-custom//etc/rc.d/in
it.d/masq/45AllowPUBDNS line 3, near "'disabled'
$OUT"
WARNING in /etc/e-smith/templates-custom//etc/rc.d/init.d/masq/45AllowPUBDNS:
(Missing operator before
$OUT?)
ERROR in /etc/e-smith/templates-custom//etc/rc.d/init.d/masq/45AllowPUBDNS: Prog
ram fragment delivered error <<syntax error at /etc/e-smith/templates-custom//et
c/rc.d/init.d/masq/45AllowPUBDNS line 3, near "'disabled'
$OUT ">> at template line 1
ERROR: Template processing failed for //etc/rc.d/init.d/masq: 2 fragments genera
ted warnings, 1 fragment generated errors
at /sbin/e-smith/expand-template line 49
[root@linux1 masq]#
-
my $status=$tinydsext{status} || 'disabled' ; <---
-
root@lanforcedsme6 var]# /etc/rc.d/init.d/tinydnsext restart
Stopping tinydnsext:svc: warning: unable to chdir to /service/tinydnsext: file does not exist
[ OK ]
Starting tinydnsext:svc: warning: unable to chdir to /service/tinydnsext: file does not exist
As far as i can tell i followed your instructions properly, however the path to the tinydns data files seems to point to /service/tinydnsext and the files are in /var/serveice/tinydnsext what have i missed?
-
the link is wrong?
-
looks like you spelled tindnsext as tinydsext leaving out an all important n from the dns part of the word. Typos will kill you every time.
-
When you set up the symbolic link for the tinydnsext did you specify the path like this?
you must set tinydnsext up as a service by issuing the command
ln -s /var/service/tinydnsext /service/tinydnsext
That is how the restart knows about the /var/service path
-
Hi all
I have written these procedures into a coupla scripts, one to install, and one to remove.
Anyone care to test them out for me?
If so please observe the following:
Please read throught the scripts first BEFORE using to review the layout and check for any basic errors (& if it looks like it will break anything).
Please only use on a test box NOT an production server.
Post back to this thread if you want to play around with this.
HTH
-
Sorry, just to follow this topic.
-
Any news on whether this is solid HowTo and what about this install/remove script does it work?
Ed
-
Hi edb
Just had my first taker to test these scripts so hopefully will have some more info soon - of course if you have the facilities to test them as well ... :-)
-
Ok....seems to work, got rid of all errormessages and it is running.
Now how do I check that it is working as supposed?
-
If I would like to change the host of the MX post do I need to change the appropriate template (setting a static value) or is there a better way?
-
Hi all
I have written these procedures into a coupla scripts, one to install, and one to remove.
Anyone care to test them out for me?
If so please observe the following:
Please read throught the scripts first BEFORE using to review the layout and check for any basic errors (& if it looks like it will break anything).
Please only use on a test box NOT an production server.
Post back to this thread if you want to play around with this.
HTH
Hi smeghead,
I am ready to test your scripts and I hope that someone make a rpm to resolve this problem of the sme.
-
Hi smeghead,
I am ready to test your scripts and I hope that someone make a rpm to resolve this problem of the sme.
-
Can I get a copy of the install/uninstall script? Thank you
-
I have sent a copy to choby as he had his email address available. Either send me an email with your address or change your preferences here to show it; a copy will then wing its way to you :-)
HTH
-
I would still like to get the install/uninstall script. Thanks
-
Hi edb
Copy on its way, enjoy!
-
Thank you ...
-
I'll test the scripts also if you wouldn't mind sendimg them my way.
jonr@destar.net in case I don't have it in my profile. :)
-
Hi Jon
Sent, enjoy
-
script please!
andrej(at)pcklinika.com
Tx,
-
Can someone make public the install/uninstall script please.
The only way to improve on it is to have it released for all to try on different systems setups, etc etc..............
So anyone gonna share it or what????????!!!!!!!!!
-
Anyone care to post their success/failure using these scripts.
Feedback so far has been positive but I'd like an update from those using them.
If there are no problems reported then I will post them for general consumption.
Any additional info on the performance of TinyDNS when run this way would also be welcome.
TIA
-
hey smeghead,
cheers for the script, gonna try it out now!
Let you know results!
-
My install failed,
not due to the script - but to the fact i had a different version of sme-server running (6.0 not 6.0.1 -)
So am almost finished downloading 6.0.1, will try it out and then post back here my results!
Other than that it all looks quite good (the script!?) :pint:
-
Hmm, I guess 6.0 should work, can you remember if there were any errors posted when the script ran?
If using a router don't forget to forward port 53 to the SME box otherwise it will never work!
HTH
-
yeah there were errors when installing it but i cant remeber them, i just tried installing on 6.0.1-01
and here is what it says
Copying working files to PUBLICDNS2157
Copy complete..............
This installation only supports SME 6.0 or higher..
exiting
and that is exactly what i get!
What could be the problem?????????????
I have port 53 tcp/udp forwarded to my sme box!
-
.. the script is saying your using MSE 6.0 not 6.0.1, I have sent you a copy with this check removed to try out.
HTH
-
i actually went through the script myself and removed the check, all it does is say
"
Copying Files...................
Completed"
or something along those lines.
Is that all it is meant to do?
-
ok i uncommented all the commands you had commented out.
all ichanged was the check
if [ $IS_SME60 -ne 0 ]
to
if [ $IS_SME60 -ne 1 ]
so in essence the install continues if it fails that check.
After that all i get is
command not found
no such file or directory
errors.
If you let me know what version you have tested your script out on that might help out a bit.
When i look at the install script it looks ok to me,
so i cant see where it could be going wrong!
-
I have sent a copy to choby as he had his email address available. Either send me an email with your address or change your preferences here to show it; a copy will then wing its way to you :-)
HTH
Dear smeghead
Can you please email me your scripts to
rallen3 at gmail dot com?
Thanks.
Robert
-
Dear smeghead
Can you please email me your scripts to geofr2003@yahoo.com?
Geo :roll:
-
hey smeg!
sorry for taking so long to reply!
It seems the script doesnt want to work on my box,
I have tried several methods;
fresh install (using script after a fresh install)
altering script (comenting out the sme version check)
and a whole lot more!
I have come to the conclusion that from the errors i receive during the install, that the fail lies in creating the directories and files in the
"/custom-templates/" directory.
So i'm not 100% sure if it is a permission problem
(shouldnt be logging in as root)
or there is a config prob with the script!
I appreciate you sending me the script to try out!
What i would like to ask is the steps you took to install it on your machine, your configration, and what (if any) extra RPM's you have installed (or need to install).
Cheers :pint:
-
Since this seems to be the distribution mechanism I would appreciate a copy as well,
many thanks
kevin
-
I am interested to hear from any user who has tried this script to see what their results were with it!
As I am sure smeghead is!
Please post your results with this script!
Cheers :pint:
-
Hi!
I'm running 6.01-01 (6.01-02 and 6.5 too but in VMware) on a dedicated server. I would like to test your scripts too.
e-mail: martijn at goudkamp.it
Thanx!
-
I have had a reports of a coupla glitches so I am gonna review the scripts and hopefully get a chance to test them on 6.5b1.
You can wait till after the w/e when (hopefully) I will have the time to do the testing or try the current version.
Email me off list about this if you want the orig ones.
HTH
-
Hi all
I have redone the scripts to eliminate a coupla stupid logic errors, doh!
They now work flawlessly for me on a clean 6.0.1 build.
If RequestedDeletion & Co can se me up with a contrib area I will post them for all to access. If you want them immedialtely just send me a message directly via the email button on this post.
Thank you all for the feedback.
-
I have redone the scripts to eliminate a coupla stupid logic errors, doh!
Thank you all for the feedback.
Hey smeg,
revised script installed perfectly!
couple of Q's!
when doing DIG @mydomain.com etc
it returns no Authorative answer!
Running with tinydnsext as a service,
shouldnt it be answering Authoratively for that domain and any domain added to my SME box?
Just wondering is all!
-
Hi,
Can you please email me your scripts to skalviai@takas.lt?
Kestutis
-
This sounds like just what I've been looking for. Aren't they setting up an area for you to post your script? Can you email me the script too?
cozmos9 at yahoo.com
Thanks a bunch!
-
and to me too...
testuser AT ccskavenger.info
I will host it if you want....
-
Hi Cosmos & skav
On their way.
I have sent a direct request for a contribs d/l folder so perhaps it will be available soon.
HTH
-
Now available from:
http://mirror.contribs.org/smeserver/contribs/gfleming/PublicDNS
Enjoy!
-
Hello Smeghead
Do you have to make any configurations in this install asking the question before i install it.
If so what parts please.
I are running my router in bridging mode do i have to open port 53 on sme server.
Ta in advance
Alan Stokes
-
Its all done for you.
The script merely consolidates the info from various post to this forum about how to set this up. As this info could be difficult or fiddly for a new user to implement without error I wrote the scripts to allow anyone to try this; I wrote the uninstall script to allow an easy removal if something didn't work as expected or something broke.
HTH
-
smeghead
Thank's for the reply very helpfull
GREATFULL
Alan Stokes
-
Hello smeghead. Please, encoded files remove.sh and shutdown_external_dns.sh to unix format. I test only for 6.0.1
Thank you for this contrib
Normando Hall
-
I tested on my 6.0.1 and it worked perfectly.
I've waited along time for something like this.
Excellent work!! Thank you
Ed
-
Quick question
Is this PubDNS contrib setup for a Primary or Secondary Name Server?
I would like to run my SME as a Secondary Name Server.
Also, when I do an "nslookup mydomain.com dnsserverIP" it returns the external IP for the mydomain.com Domain. But if I do an "nslookup www.mydomain.com dnsserverIP" it resolves to the internal IP for the www.mydomain.com. Why?
BTW: www.mydomain.com is a site I'm hosting
(I created a Domain in server manager then created an ibay "mydomain.com" to link to)
Should the Hostnames & addresses section of server manager be set to "Global|self" or "Global|local" specifying the internal IP & Global/external IP?
I do have it registered as a NameServer with the registar.
Thanks
Ed
-
I also get these errors in /var/log/messages when I try to create a new Domain or delete an existing Domain
Can't exec "/etc/e-smith/events/domain-delete/S51update-dnsext": Permission denied at /usr/lib/perl5/site_perl/esmith/event.pm line 124.
Can't exec "/etc/e-smith/events/domain-create/S51update-dnsext": Permission denied at /usr/lib/perl5/site_perl/esmith/event.pm line 124.
-
.. I'll try to make some time to check this out, I would guess some sorta perms prob but will look into it further.
-
Anyone else have the problem of the PubDNS is resolving to an internal IP when it should be pointing to the external IP?
-
Since I have received no replies to my messages I can only gather that no one else has tested this and no one knows how to fix it.
I presumed that because the install went fine (which seemed to be the biggest issue according to the thread)that it would do what it was suppose to do according to the name (act as a public DNS server).
Silly me :hammer:
I would not suggest that anyone bother installing this contrib until it can actually display the external IP to the rest of the world the way it should when resolving domains.
-
I installed this and works as promised, except that as edb pointed out "domain.com" is listening on the external IP but "www.domain.com" is pointing to the internal IP.
smeghead help us please!
-
Hmm, I will check this out this w/e and post back as soon as I can; feel free to prod me with a reminder next week if I haven't replied :-)
-
Thanks smeaghead,
I wonder if this has to do with my box, I did not use the script for the install and followed both how-to and the instructions you provided with the zipped files. I'll be breaking my head in meantime :hammer:
Regards,
-
So to make it work right, you need to edit the file
/etc/e-smith/templates-custom/var/service/tinydnsext/root/data/60hostARecords
and modify
if ($hosttype eq 'Self')
{
$anIP = $LocalIP;
by
if ($hosttype eq 'Self')
{
$anIP = $ExternalIP;
then
/sbin/e-smith/expand-template /var/service/tinydnsext/env/IP
/sbin/e-smith//expand-template /var/service/tinydnsext/root/data
cd /var/service/tinydnsext/root
/usr/local/bin/tinydns-data
/etc/rc.d/init.d/tinydnsext restart
And www.domain, ftp.domain, mail.domain, etc. all should now work.
Thank you all,
-
.. good catch stuntshell, I will update accordingly
-
While searching the forum I found this thread.
It looks that I have the same problem as "stuntshell".
I didn't install the stuf you're talking about.
It is a new installation.
I am using dyndns.org.
The "Primary" domain is (domain1.dyndns.org)
I added a second domain (domain2.dyndns.org)
I made an ibay for (domains2)
- dom2
- admin
- write=group, read=everyone
- Entire internet / no password
- CGI enabled
I created a "Domains"
- Domain name: (domain2.dyndns.org)
- Content: I selected the ibay for (domain2.dyndns.org)
I created a "Hostnames and addresses" for (domain2.dyndns.org)
The primary domain (domain1.dyndns.org) works perfectly.
http://www.domain1.dyndns.org
http://domain1.dyndns.org
I installed Xoops "xoops_2013fr" in it, same version as for (domain1.dyndns.org).
All went well.
I rename index.html to index.html.sme.org
In my browser I can go to (http://domain2.dyndns.org) but not to (http://www.domain2.dyndns.org).
www.domain2.dyndns.org could not be found. Please check the name and try again."
I looked into httpd.conf and somewhere it says: user www and group www.
I (chown -R www:www *) but same problem.
I looked into Primary and it was (root:www).
I (chown -R root:www *) but same problem.
The permissions inside ibays:
drwxr-xr-x 6 root root 4096 Jul 15 08:59 awstats
drwxr-xr-x 7 root root 4096 Jul 19 11:39 Primary (for domain1)
drwxr-xr-x 7 root root 4096 Jul 21 23:32 dom2 (for domain2)
The permissions inside dom1:
drwxrwsr-x 2 root www 4096 Nov 19 2003 cgi-bin
drwxrwsr-x 3 root www 4096 Jul 7 10:11 docs
drwxrwsr-x 2 root www 4096 Nov 19 2003 files
drwxrwsr-x 14 root www 4096 Jul 22 12:12 html
-rw-rw-r-- 1 root www 1868854 Jul 16 12:23 xoops_2013fr.zip
This thing is driving me crazy.:hammer:
Any help appreciated.
Thank you.
Michel-Andre
-
Michel,
If you're using dyndns, then that's where you name resolution lies, to make domain2 work you would need to create another account with them and point to your server. After that your server would know how to handle the directories to show. This thread is about having your own nameserver, where you register a domain and point to your SME and let it do the job.
-Aboout your issues with xoops:
Are you using your server in server/gateway mode? If so, and having SME as your DNS server inside your network, whatever domains you add to it, should resolve locally. The problems are not related to your permissions.
Hope this helps,
-
Sorry stuntshell about dropping into a thread like that but this is the only place where there is somebody having the same problem. I looked into many other places and I didn't find a solution.
I am using the server as server&gateway
I have another server somewhere else and I have the same problem. So this time I decided to solve the problem.
That other server is also using dyndns for another domain than the Primary and it is using both domains name in the same account at dyndns.
Last night, I aslo thought that is was because there were 2 domains under the same account at dyndns so I had a friend to create another account at dyndns so I can try with only 1 domain by account. I have the same problem. So I don't think it is because of the 2 domains under the same account.
I am not at the location of that server. I worked from home.
I ssh to the remote server and I can locally ping both (www.domain2.dyndns.org) and (domain2.dyndns.org). So the server should be OK.
From home I can ping (domain2.dyndns.org) but not (www.domain2.dyndns.org): unknown host www.domain2.dyndns.org . So it looks like dyndns.org has something wrong but it is working for the Primary and not for the second domain. Both are configured the same standard way.
In httpd.conf:
<VirtualHost 0.0.0.0:80>
ServerName www.domain2.dyndns.org
ServerAlias domain2.dyndns.org toto.domain2.dyndns.org
DocumentRoot /home/e-smith/files/ibays/dom2/html
ScriptAlias /cgi-bin /home/e-smith/files/ibays/dom2/cgi-bin
Alias /files /home/e-smith/files/ibays/dom2/files
Everything looks good both at dyndns.org and at the server. There is something I am missing.
If I cannot find something then I will try to do my own dns server but this is quite something and I would like to solve my problem until I can do my own dns server.
Again I am sorry to drop in like that but as I wrote above it is the only place I found with the exact same problem. If this is a problem or an inpoliteness, please tell me and I will not post again.
Michel-André
-
Maybe I found something and I think it is quite weird.
I use lynx to acces (hhtp://www.domain2.dyndns.org) and I ended up at (org.com).
At the bottom of that page there is a link:(Information on how you reached this site), I clicked on it and this is the message:
******************************************
Org.com [transpar.gif]
Only the best links ...
HOTELS | CREDIT CARDS | LOANS | GIFTS | GAMBLING | INVESTING | EDUCATION | HEALTH &
FITNESS | FLOWERS
Occasionally we receive inquiries from users who do not understand why they have accessed our site.
Please be advised that you are not reaching our site as a result of spyware. We are not exactly sure
why you have been directed here, however, we believe it is a result of the autosearch feature of
Internet Explorer. If a site entered into the address bar cannot be accessed, Explorer apparently
appends ".com" to the name and then tries to access that site. In the case of a search ending in
.org, Explorer thus accesses our domain, "org.com." If you wish to turn off this behavior, we think
it can be successfully accomplished by doing the following:
1. From the "Tools" menu, select "Internet Options".
2. Click on the "Advanced" tab.
3. Under "Search from the Address Bar", select "Do not search from the Address bar".
4. Click "OK".
5. You may need to restart your computer.
Please note that this does not solve the problem of why you could not access the original search
term, and if that site is still not accessible (due to DNS problems, a server being down, network
problems, a typographical error, etc.) you should now receive an error that the page cannot be
displayed.
HOTELS | CREDIT CARDS | LOANS | GIFTS | GAMBLING | INVESTING | EDUCATION | HEALTH &
FITNESS | FLOWERS
Copyright 2005, Org.com
******************************************
I never heard of such a thing.
If I use lynx again and I type the address of the other server which have the same problem, I end up at the same url.
Is there somebody who ever saw that?
Michel-Andre
-
Michel,
This proves once again you're having name resolution problems. You've already mention you're using the gateway mode, another question would be about the DNS, are you using SME as DNS or did you set up to use from your provider?
I don't mean to be rude, or anything like that, but it would be best if you create another topic with these issues, so we can keep things organized. Also it would be easier for other people to help, since they will read the subject and maybe know exactly what your problem may be.
Regards and good luck!
-
I send an email to dyndns explaining the situation. I just recieved an answer that solve the problem.
You have the 'wildcard' feature disabled for your 'domain2.dyndns.org' host, you need to have that feature enabled for 'www.domain.dyndns.org' to resolve to your IP address. You can enable the wildcard setting on the configuration page for your 'domain2.dyndns.org'
host.
A real newbie mistake. :oops:
I hope it will help others.
Thank you for your patience stuntshell.
Michel-André :pint: