+- Linux-Noob Forums (https://www.linux-noob.com/forums)
+-- Forum: Distro Noob (https://www.linux-noob.com/forums/forum-10.html)
+--- Forum: Fedora (https://www.linux-noob.com/forums/forum-94.html)
+---- Forum: Fedora Core Release 4 (https://www.linux-noob.com/forums/forum-42.html)
+---- Thread: bind and fedora core 4 (/thread-2377.html)
bind and fedora core 4 - cyris - 2005-10-16
Hello all. I am attempting to run BIND on fedora core 4 and having some issues.
I have added my zone file to /etc/named.conf.
Here is a copy of my named.conf...
options {
directory "/var/named";
version "xxx";
};
zone "thewildgoose.ca" {
type master;
file "data/named.xxxx.ca";
};
I am just trying to get forward dns working, I will take care of reverse after.
This is my zone file...
$TTL 1d
@ IN SOA xxxxx.ca. xxxx.xxxx.ca. (
2005081001;serial
3600 ;refresh
300 ;retry
3600000 ;expire
3600 ) ;minimum
IN NS ns1.xxxx.ca.
$ORIGIN xxxx.ca.
;A Records
ns1 IN A xx.xx.xx.xx
mail IN A 68.151.33.239
@ IN A 68.151.33.239
;CNAME Records
www IN CNAME ns1
webmail IN CNAME ns1
xxxx.ca. IN MX 1 mail
/var/log/messages seems to indicate named starts fine but i cant seem to connect to any of my hosts.
thanks for reading this and i look forward to any advice.
bind and fedora core 4 - hijinks - 2005-10-16
it really helps if we know the real domain and IP info for the zone
bind and fedora core 4 - cyris - 2005-10-16
Quote:it really helps if we know the real domain and IP info for the zoneIP Address = 68.151.33.239
Domain = thewildgoose.ca.
Forwarding port 53 UDP to 192.168.2.2
#cat /var/log/message
Oct 16 13:47:53 localhost named[9525]: starting BIND 9.3.1
Oct 16 13:47:53 localhost named[9525]: loading configuration from '/etc/named.conf'
Oct 16 13:47:53 localhost named[9525]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 16 13:47:53 localhost named[9525]: listening on IPv4 interface eth0, 192.168.2.2#53
Oct 16 13:47:53 localhost named[9525]: command channel listening on 127.0.0.1#953
Oct 16 13:47:53 localhost named[9525]: command channel listening on ::1#953
Oct 16 13:47:53 localhost named[9525]: zone thewildgoose.ca/IN: loaded serial 2005101601
Oct 16 13:47:53 localhost named[9525]: running
Oct 16 13:47:53 localhost named[9525]: zone thewildgoose.ca/IN: sending notifies (serial 2005081001)
bind and fedora core 4 - hijinks - 2005-10-17
ok you are behind a nat.. so is port 53 both tcp/udp behind forwarded?
also can you do this on the server
nslookup thewildgoose.ca 127.0.0.1
bind and fedora core 4 - cyris - 2005-10-18
Quote:ok you are behind a nat.. so is port 53 both tcp/udp behind forwarded?
also can you do this on the server
nslookup thewildgoose.ca 127.0.0.1
I should of mentioned this before, I'm behind an IPCOP transparent proxy with just UDP 53 forwarded to my fedora box. I was under the impression that TCP 53 was reserved for seconday name server transfers, is that true?
the lookup was successful.
bind and fedora core 4 - cyris - 2005-10-18
Quote:<blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-username="hijinks" data-cite="hijinks" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="1852" data-ipsquote-contentclass="forums_Topic"><div>ok you are behind a nat.. so is port 53 both tcp/udp behind forwarded?
also can you do this on the server
nslookup thewildgoose.ca 127.0.0.1
I should of mentioned this before, I'm behind an IPCOP transparent proxy with just UDP 53 forwarded to my fedora box. I was under the impression that TCP 53 was reserved for seconday name server transfers, is that true?
the lookup was successful.
</div></blockquote>
got it working. thought I forwarded UDP 53 when it was actually TCP 53