Hi,
I'm having a problem setting up BIND on FreeBSD, I need it to answer authoritatively for a particular domain. I believe I have it working but for some reason when I do an nslookup and set my server to that domain the nslookup just times out.
Here is a sample of my named.conf file
options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
recursion no;
listen-on { someip; };
query-source address * port 53;
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "master/localhost.rev";
};
// RFC 3152
zone "1.0.0.0.0.0.0.0.0.0.0.0.0
{
type master;
file "master/localhost-v6.rev";
};
//An example master zone
zone "somedomain.com" {
type master;
file "master/somedomain.com";
};
zone "1.168.192.in-addr.arpa" {
type slave;
file "slave/1.168.192.in-addr.a
masters {
192.168.1.1;
};
};
Any ideas anyone?
Cheers,
Mark
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Oddly enough I did that and don't seem to have any log files being generated. I apparently can do an nslookup against the localhost but for some reason from another box when I do
nslookup
>server someip
>somedomain
I get
;; connection timed out; no servers could be reached
Yet nothing is written to the log.
Thanks for your help :)
Cheers,
Mark
1) Remote host is in the same LAN?
2) What if you try nslookup on DNS but with external ip address as server's IP address?
3) Are you sure, that 'listen-on { someip; };' really refers to external IP (not 127.0.0.1)?
4) How do you reload your named?
5) If not a secret, post entire 'named.conf', and '/etc/named/master/somedom
For debug purposes stop your named and run it in debug mode in forground: '/usr/sbin/named -d 1 -f'
(you can exit from it with Ctrl-\ keys). Also it would be nice if you post debug output here.
1) Remote host is not on the same lan.
2) It appears to work
3) The listen-on is an external IP, the servers are located within a data center and I'm sitting in our office
4) I reload named by using /etc/rc.d/named stop /etc/rc.d/named start or sometimes using /etc/rc.d/named restart
5) It isn't really a state secret but I'd rather not give out the information.
With running named in the foreground with debug mode, I get absolutely nothing.
Ok, if 2) works, than named is started as it should start. What is named version?
Now your named may not accept quierying by it's policy, then you should add more options like 'allow-query' to your named.conf. But usually with such config server responds as 'refused', not as 'timed out'
Or you may have no network connectivity for DNS with remote client. To check, run 'tcpdump udp port 53', then run remote query, then see does it appear on your DNS's interface.
The named version is 9.3.3.
With tcpdump udp port 53
I get
listening on em0, link-type EN10MB (Ethernet), capture size 96 bytes
When I do it from a box sitting in the data center next to this one I get a response
00:22:11.408552 IP validdomain.com.49577 > othervaliddomain.com.domai
However when I do it from my local server here in the office I get absolutely nothing
This is what I get with the -g option I didn't get anything even with the higher debug level
28-Apr-2007 00:26:24.479 loading configuration from '/etc/namedb/named.conf'
28-Apr-2007 00:26:24.479 set maximum stack size to 67108864: success
28-Apr-2007 00:26:24.479 set maximum data size to 536870912: success
28-Apr-2007 00:26:24.479 set maximum core size to 9223372036854775807: success
28-Apr-2007 00:26:24.479 set maximum open files to 11095: success
28-Apr-2007 00:26:24.480 listening on IPv4 interface em0, 66.11.150.5#53
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: create
28-Apr-2007 00:26:24.480 could not listen on UDP socket: address in use
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: destroy
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: clientmgr_destroy
28-Apr-2007 00:26:24.480 creating IPv4 interface em0 failed; interface ignored
28-Apr-2007 00:26:24.480 listening on IPv4 interface lo0, 127.0.0.1#53
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: create
28-Apr-2007 00:26:24.480 could not listen on UDP socket: address in use
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: destroy
28-Apr-2007 00:26:24.480 clientmgr @0x81a7c80: clientmgr_destroy
28-Apr-2007 00:26:24.480 creating IPv4 interface lo0 failed; interface ignored
28-Apr-2007 00:26:24.480 not listening on any interfaces
28-Apr-2007 00:26:24.481 could not get query source dispatcher (0.0.0.0#53)
28-Apr-2007 00:26:24.481 additionally listening on IPv4 interface em0, 66.11.150.5#53
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: create
28-Apr-2007 00:26:24.481 could not listen on UDP socket: address in use
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: destroy
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: clientmgr_destroy
28-Apr-2007 00:26:24.481 creating IPv4 interface em0 failed; interface ignored
28-Apr-2007 00:26:24.481 additionally listening on IPv4 interface lo0, 127.0.0.1#53
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: create
28-Apr-2007 00:26:24.481 could not listen on UDP socket: address in use
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: destroy
28-Apr-2007 00:26:24.481 clientmgr @0x81a7240: clientmgr_destroy
28-Apr-2007 00:26:24.481 creating IPv4 interface lo0 failed; interface ignored
28-Apr-2007 00:26:24.481 load_configuration: address in use
28-Apr-2007 00:26:24.481 loading configuration: address in use
28-Apr-2007 00:26:24.481 exiting (due to fatal error)
> With tcpdump udp port 53 I get
That means you have firewall somwhere between your local office and datacenter, that doen't allow DNS queries to that host. Where is this firewall located - I don't know.
> 28-Apr-2007 00:26:24.481 exiting (due to fatal error)
Because another version ot named is already running to run debug session, '/etc/rc.d/named stop; pkill named' then run again in a forground.
But you get nothing if you don't see DNS packets on your interface when query from outside. And you can nothing to do with it unless you find who drops that packets.
Business Accounts
Answer for Membership
by: NopiusPosted on 2007-04-27 at 19:26:06ID: 18993265
Did you open udp/tcp port 53 on a firewall of your FreeBSD box?
What named writes to log file (if firewall is OK)?