bind problem
i've configured dns server in freeBSD 6.1 but when i query the server it wont resolve my domain name. i've added in resolv.conf also and my bind daemon is also running without any errors. i couldnt figure out the problem. if any suggestion please help me ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind problem
Hi Robin, On Tuesday 10 October 2006 16:22, Robin Tiwari wrote: i've configured dns server in freeBSD 6.1 but when i query the server it wont resolve my domain name. i've added in resolv.conf also and my bind daemon is also running without any errors. i couldnt figure out the problem. if any suggestion please help me Can you send us your configuration files (or at least the important parts of them)? -- Lothar pgph5hHaogxsc.pgp Description: PGP signature
Re: Bind problem
Hi, The installed bind is not in /usr/local/bin that is where the port is installed. You might want to do a: # which bind and set rc.conf to the right value for the program. -Derek At 04:34 PM 7/10/2006, Lisa Casey wrote: - Original Message - From: Jonathan Chen [EMAIL PROTECTED] To: Lisa Casey [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, July 10, 2006 3:43 PM Subject: Re: Bind problem Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? Yes. /etc/rc.conf has the following lines for named: named_enable=YES named_program=/usr/local/sbin/named named_flags=-u bind -g bind -c /etc/namedb/named.conf Lisa Casey This actually didn't quite answer the problem, but it did lead me in the right direction to solve it. which bind, of course, doesn't work and which named just gives me the path to the named executable as given in /etc.rc.conf But, this got me to thinking so I did a find / -name named -print And found something interesting. I have named executables in both /usr/local/sbin and /usr/sbin So I changed the line in /etc/rc.conf that read: named_program=/usr/local/sbin/named to named_program=/usr/sbin/named and rebooted the box. So far, so good. named -v gives me BIND 9.3.0 and in /var/messages the reboot info shows the same when named loads: Jul 11 13:40:50 netlink kernel: Mounting root from ufs:/dev/da0s1a Jul 11 13:40:50 netlink named[293]: starting BIND 9.3.0 -u bind -c /etc/namedb/n amed.conf -t /var/named Jul 11 13:40:51 netlink named[293]: command channel listening on 127.0.0.1#953 (It's also picking up the command channel, so I guess I did that right). I have one last problem (or at least I hope so!). I maybe ought to ask this in a bind newsgroup, but there are enough folks on this list running bind on FreeBSD that someone ought to know. Evidently Bind 9 doesn't like my zone files whereas Bind 8 was OK with them. A little background: My main domain name is jellico.comI also host several virtual domains using IP based virtual domains in Apache2. So each of my virtual domains has been assigned an IP address out of my Class C. In /etc/namedb/M (the directory where I keep my zone files that this DNS server is master for) I have (among other zones) jellico.com.db which is my forward file for the domain and 26.44.208.in-addr.arpa which is the reverse zone file for the domain. I have always had my virtual domains configured into my forward file (jellico.com.db) so as to enable forward DNS resolution on those. They are configured into jellico.com.db like this: jellico.tn.us. IN A 208.44.26.225 multi-226 IN A 208.44.26.226 multi-227 IN A 208.44.26.227 multi-228 IN A 208.44.26.228 multi-229 IN A 208.44.26.229 multi-230 IN A 208.44.26.230 tspma.com. IN A 208.44.26.231 copperhill.com. IN A 208.44.26.232 multi-233 IN A 208.44.26.233 www.jellico.net.IN A 208.44.26.234 multi-235 IN A 208.44.26.235 stair-way-to-heaven.com.IN A 208.44.26.236 multi-237 IN A 208.44.26.237 kcsvo.com. IN A 208.44.26.238 multi-239 IN A 208.44.26.239 multi-240 IN A 208.44.26.240 wingsofvictorychurch.org. IN A 208.44.26.241 multi-242 IN A 208.44.26.242 multi-243 IN A 208.44.26.243 There are a few others, but you get the idea. I have also always had my virtual domains setup in my reverse file so as to enable reverse DNS resolution on these. This section of my reverse file looks like so: 225 IN PTR jellico.tn.us. 226 IN PTR multi-226.jellico.com. 227 IN PTR multi-227.jellico.com. 228 IN PTR multi-228.jellico.com. 229 IN PTR multi-229.jellico.com. 230 IN PTR multi-230.jellico.com. 231 IN PTR tspma.com. 232 IN PTR copperhill.com. 233 IN PTR multi-233.jellico.com. 234 IN PTR www.jellico.net. 234 IN PTR multi-234.jellico.com. 235 IN PTR multi-235.jellicocom. 236 IN PTR stairway-to-heaven.com. Bind 9 is OK with my reverse file, but it doesn't like any entry in my forward file that ends in a dot (so as not to append jellico.com to it). When I rebooted the box, as soon as the nameserver loads I get these error messages in /var/messages: Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:222: ignoring out-of-zone d ata (mail.campbellcounty.com) Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:224: ignoring out-of-zone d ata (campbellcounty.com) Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:522: ignoring out-of-zone d ata (jellico.tn.us) Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:528: ignoring out
Re: Bind problem
Lisa, Your forward file should be something like this: $TTL3600 @ IN SOA ns.jellico.com. dnsadmin.jellico.com. ( 2003071101 ; serial 3H ; refresh 1H ; retry 1W ; expiry 1D ); minimum ; DNS Servers @ IN NS ns.jellico.com. @ IN NS ns2.jellico.com. ; Machine Names localhost IN A127.0.0.1 mailIN A208.44.26.225 pop IN A208.44.26.225 @ IN A208.44.26.225 ; Aliases www IN CNAME@ ww IN CNAME@ w IN CNAME@ ; MX Record @ IN MX 10 mail.jellico.com. Just correct the IP's and add the rest of your hosts, and correct any names that may be incorrect. Make sure you name the file the same as bind is looking for in: /etc/namedb/named.conf If you have specific questions to any of the file entries you can email me directly. -Derek At 01:20 PM 7/11/2006, Lisa Casey wrote: Hi, The installed bind is not in /usr/local/bin that is where the port is installed. You might want to do a: # which bind and set rc.conf to the right value for the program. -Derek At 04:34 PM 7/10/2006, Lisa Casey wrote: - Original Message - From: Jonathan Chen [EMAIL PROTECTED] To: Lisa Casey [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, July 10, 2006 3:43 PM Subject: Re: Bind problem Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? Yes. /etc/rc.conf has the following lines for named: named_enable=YES named_program=/usr/local/sbin/named named_flags=-u bind -g bind -c /etc/namedb/named.conf Lisa Casey This actually didn't quite answer the problem, but it did lead me in the right direction to solve it. which bind, of course, doesn't work and which named just gives me the path to the named executable as given in /etc.rc.conf But, this got me to thinking so I did a find / -name named -print And found something interesting. I have named executables in both /usr/local/sbin and /usr/sbin So I changed the line in /etc/rc.conf that read: named_program=/usr/local/sbin/named to named_program=/usr/sbin/named and rebooted the box. So far, so good. named -v gives me BIND 9.3.0 and in /var/messages the reboot info shows the same when named loads: Jul 11 13:40:50 netlink kernel: Mounting root from ufs:/dev/da0s1a Jul 11 13:40:50 netlink named[293]: starting BIND 9.3.0 -u bind -c /etc/namedb/n amed.conf -t /var/named Jul 11 13:40:51 netlink named[293]: command channel listening on 127.0.0.1#953 (It's also picking up the command channel, so I guess I did that right). I have one last problem (or at least I hope so!). I maybe ought to ask this in a bind newsgroup, but there are enough folks on this list running bind on FreeBSD that someone ought to know. Evidently Bind 9 doesn't like my zone files whereas Bind 8 was OK with them. A little background: My main domain name is jellico.comI also host several virtual domains using IP based virtual domains in Apache2. So each of my virtual domains has been assigned an IP address out of my Class C. In /etc/namedb/M (the directory where I keep my zone files that this DNS server is master for) I have (among other zones) jellico.com.db which is my forward file for the domain and 26.44.208.in-addr.arpa which is the reverse zone file for the domain. I have always had my virtual domains configured into my forward file (jellico.com.db) so as to enable forward DNS resolution on those. They are configured into jellico.com.db like this: jellico.tn.us. IN A 208.44.26.225 multi-226 IN A 208.44.26.226 multi-227 IN A 208.44.26.227 multi-228 IN A 208.44.26.228 multi-229 IN A 208.44.26.229 multi-230 IN A 208.44.26.230 tspma.com. IN A 208.44.26.231 copperhill.com. IN A 208.44.26.232 multi-233 IN A 208.44.26.233 www.jellico.net.IN A 208.44.26.234 multi-235 IN A 208.44.26.235 stair-way-to-heaven.com.IN A 208.44.26.236 multi-237 IN A 208.44.26.237 kcsvo.com. IN A 208.44.26.238 multi-239 IN A 208.44.26.239 multi-240 IN A 208.44.26.240 wingsofvictorychurch.org. IN A 208.44.26.241 multi-242 IN A 208.44.26.242 multi-243 IN A 208.44.26.243 There are a few others, but you get the idea. I have also always had my virtual domains setup in my
Bind problem
Hi All, I seem to have a bit of a problem with my Bind installation on FreeBSD 5.3. When I first setup this box, I installed the Bind 8.4 from the ports. Soon afterwards, I decided to go with Bind 9 so I installed that from the ports. Now Bind seems to have an identity problem. When I boot the box I get this in /var/log/messages: Jul 10 15:05:32 netlink named[292]: starting (/etc/namedb/named.conf). named 8. 4.4 Thu Sep 22 14:07:24 EDT 2005 [EMAIL PROTECTED]:/usr/ports/dns/ bind84/work/src/bin/named Jul 10 15:05:32 netlink named[292]: limit files set to fdlimit (1024) Jul 10 15:05:32 netlink named[292]: /etc/namedb/named.conf:104: Ignoring BIND 9 inet control clause Jul 10 15:05:32 netlink named[293]: Ready to answer queries. When I do a named -v to see which version of Bind is running I get this: netlink# named -v BIND 9.3.0 ndc (a Bind 8 program) doesn't work, I get this error: netlink# ndc Type help -or- /h if you need help. ndc help (builtin) start - start the server (builtin) restart - stop server if any, start a new one ndc: error: ctl_client: evConnect(fd 3): No such file or directory ndc: error: cannot connect to command channel (/var/run/ndc) And rndc doesn't work either: netlink# rndc stop rndc: connect failed: connection refused netlink# rndc start rndc: connect failed: connection refused netlink# rndc status rndc: connect failed: connection refused I'm not exactly sure how I created this mess, but what would be the best way to fix this? I really want to be running Bind 9. Thanks, Lisa Casey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind problem
On Mon, Jul 10, 2006 at 03:11:41PM -0400, Lisa Casey wrote: Hi All, I seem to have a bit of a problem with my Bind installation on FreeBSD 5.3. When I first setup this box, I installed the Bind 8.4 from the ports. Soon afterwards, I decided to go with Bind 9 so I installed that from the ports. Now Bind seems to have an identity problem. Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? -- Jonathan Chen [EMAIL PROTECTED] --- I love deadlines. I like the whooshing sound they make as they fly by - Douglas Adams ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind problem
- Original Message - From: Jonathan Chen [EMAIL PROTECTED] To: Lisa Casey [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, July 10, 2006 3:43 PM Subject: Re: Bind problem Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? Yes. /etc/rc.conf has the following lines for named: named_enable=YES named_program=/usr/local/sbin/named named_flags=-u bind -g bind -c /etc/namedb/named.conf Lisa Casey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind problem
On Monday 10 July 2006 13:34, Lisa Casey wrote: - Original Message - From: Jonathan Chen [EMAIL PROTECTED] To: Lisa Casey [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, July 10, 2006 3:43 PM Subject: Re: Bind problem Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? Yes. /etc/rc.conf has the following lines for named: named_enable=YES named_program=/usr/local/sbin/named named_flags=-u bind -g bind -c /etc/namedb/named.conf Lisa Casey Bind 9 doesn't use the -g flag in the same way bind 8 used to. From named(8) -g Run the server in the foreground and force all logging to stderr. Try dropping the -g bind flag from rc.conf I remember having a similar problem a while back when I switched to bind9. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpknzVdYFEvJ.pgp Description: PGP signature
Re: Bind problem
The installed bind is not in /usr/local/bin that is where the port is installed. You might want to do a: # which bind and set rc.conf to the right value for the program. -Derek At 04:34 PM 7/10/2006, Lisa Casey wrote: - Original Message - From: Jonathan Chen [EMAIL PROTECTED] To: Lisa Casey [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Monday, July 10, 2006 3:43 PM Subject: Re: Bind problem Did you remember to add: named_program=/usr/local/sbin/named to /etc/rc.conf? Yes. /etc/rc.conf has the following lines for named: named_enable=YES named_program=/usr/local/sbin/named named_flags=-u bind -g bind -c /etc/namedb/named.conf Lisa Casey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
smbd bind problem
Alright, looked at the log file. Seems the bind to *:139 is failing. Nmbd is already bound to 139, so what's the solution? Which one is supposed to be bound to 139? Someone please advise. It seems that smbd will not run. It will not run from inetd.conf. It will not run from the command line. Which is to say, it won't remain running, even with the -D switch. Nmbd runs fine from both. The server appears in the windows network browser and is pingable by netbios name. If I try to access the machine I get the following error. The account is not authorized to log in from this station. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smbd bind problem
# Dennis Olvany: Alright, looked at the log file. Seems the bind to *:139 is failing. Nmbd is already bound to 139, so what's the solution? Which one is supposed to be bound to 139? Someone please advise. Afaict the default ports are 137/udp for nmbd and 139/tcp (SMB over NetBIOS) and 445/tcp (plain SMB) for smbd. It seems that smbd will not run. It will not run from inetd.conf. It will not run from the command line. Which is to say, it won't remain running, even with the -D switch. Not surprising, it'll probably suicide after bind(2) fails. Regards, Mario ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
