FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey thanks, that first line worked and got it back up and running again,
Now I have nameserver up and running, zone files done, do I have to actually configure apache before I can access my webserver via www.tech-magic.net ? I noticed that right now I can ns1.tech-magic.net and access webserver.
since you can access your website using ns1.tech-magic.net and httpd didnt complain during boot up, usually have a message of something like the fully qualified domain error, why not try to put a canonical name in your record.
Sir, I have that in my records.
I've been studying this for hours every day, as I'm excited to get up & running, since the middle of last month, no matter how many how toos I read, copy, etc. It just doesn't want to work. After so much studying I've pretty much have it memorized how to do everything, yet It just doesn't work. I think I'm just missing something simple... Please Help...
Here is what my forward & reverse files look like.
; This file is Tech Magic's /var/named/tech-magic.forward
$TTL 86400
@ IN SOA ns1.tech-magic.net.
hostmaster.tech-magic.net. (
20040610019 ;Serial#
28800 ;Refresh
7200 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
NS ns1.tech-magic.net.
A 64.91.63.93
www CNAME ns1
email CNAME ns1
reverse:
This file is: /var/named/tech-magic.rev
$TTL 86400
@ IN SOA ns1.tech-magic.net.
hostmaster.tech-magic.net. (
20040610019 ;Serial#
28800 ;Refresh
7200 ;Refresh
604800 ;Expire
86400 ;Minimum TTL
)
It does look a little different on this forum however. I also noticed that when I'm on my server I can type www.tech-magic.net in the address bar & it comes up, but only on the web server. I used to run windows IIS 5 server & 2000 advanced server DNS, I still have all the same ports forwarded on my router just the same, I also DMZ'd this webserver and it made no difference.
well you know i am newbie too, so do not expect that i can help here..:-), it just happen that i have noticed this thread goes for almost three weeks now.
i have a running Web, DNS on Fedora and did not encounter much trouble during setup.
the only problem i got on configuring DNS is when i try to put all my configuration and zone file on the default location which is /etc/ and /var/named/ respectively. and realize that my rootdir on /etc/sysconfig/named is pointing to ROOTDIR=/var/named/chroot, and of course always forgot to change serial number after the modification of zone files...lol.
and with regards to httpd, i was able to run it just by adding a fully qualified domain, and play around with virtual hosting feature.
anyway, hope experts here would come up and give us advise on how this could be solved.
My /etc/sysconfig/named is pointing to ROOTDIR=/var/named/chroot
also, that really sucks, the fedora book I bought to get fedora core 1 doesn't even mention doing anything with that file, then /etc/named.conf says: directory "/var/named"; "that's damn decieving"
So how can I overcome this problem? I just don't know what to do, the tutorials never mention this stuff either, the other advice I get is go here and there read this and that, it all says the same stuff and none of it is working, except Linner's advice so far. Thanks Linner
so you better copy all your zone files to /var/named/chroot/var/named directory and your named.conf, rndc.key and other configuration files (if there are more) on /var/named/chroot/etc
im still reading info about dns, wow a lot to read tsk tsk.
As soon as I cd into the /var/named/chroot/etc directory and then vi named.conf, then copied text out of original and put into my new file, I noticed that named quit running and will not fire back up, How can I fix this?
eg: I'm now back to rndc:connect failed: connection refused
I removed rndc.conf & rndc.key from the /etc/ directory, now when trying to restart named it says
rndc: neither /etc/rndc.conf nor /etc/rndc.key was found
Technically after doing everything as per the documentation my nameserver should be up & running...
is there any documentation out there on any distribution that actually works?
If I reinstall fedora and just cp /etc/rndc.key /var/named/chroot/etc/rndc.key , so I can get named to run, then vi into /etc/named.conf and change the directory to: tell it that the zone files are in /var/named/chroot/var/named
I just noticed I can go to add and remove programs and uninstall the chroot tree for bind nameserver, will this get rid of the problem?
What files could i modify to get around all the chroot stuff that doesn't seem to allow bind to work?
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;
};
//
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
<-- the bolded entry is the one I'm talking about.
Your problem with not being able to connect to your web server using www was simply a zone file problem, put the files back as they were see if named will start then we can sort it out
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.