Hey guys,

I installed DNS on my linux machine (Fedora 12) using yum. I then went and started the DNS service "sudo service named start" and it appears to be running. I can telnet to port 53 from the linux machine "telnet localhost 53" but I cannot reach it from another machine on the same network "Telnet IP 53", it then gives a connection refused. I'm sure i've disabled the firewall, but I can telnet into port 80 when httpd is running from the remote machine.

Any ideas on what I could be doing wrong?
Obviously when I have another machine set to use the linux box as a DNS server it doesn't work.

Thanks for any help.

Check the f/w (iptables) on both machines. Are they on the same LAN segment; no other system in between?

sudo iptables -nvL

Hi thanks for the quick response.

The other machine I'm trying to connect to it from is a Windows 7 machine. My linux machine is actually running in VMware workstation on this computer. So Windows 7 is the host and Fedora 12 is the guest or virtual machine.

The results from iptables -nvL is below.

sudo iptables -nvL
Chain INPUT (policy ACCEPT 15628 packets, 23M bytes)
pkts bytes target prot opt in out source destination


Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination


Chain OUTPUT (policy ACCEPT 7962 packets, 327K bytes)
pkts bytes target prot opt in out source destination

I've disabled the firewall in the system-config-firewall in the gui.

Thanks

Would windblows 7 be stopping DNS queries to other machines than
the one(s) it has knowledge of as being its authoritative ones?

Just a thought - since the iptables rules accept anything (and you
must have failed to disable them [or you didn't reboot since you
disabled iptables).



Cheers,
Tink

I quickly went ahead and created another linux virtual machine and installed DNS on it, disabled the firewall, and tested it - same issue.

The two linux machines can't connect to 53 however I started apache on both and they can telnet to those two fine. Obviously there's something I'm doing wrong. Really the only thing I'm doing is installing bind through yum and then started the service. Obviously there are additional configuration steps that could be done, but I would think that you should still be able to telnet to the port/service.

That is indeed another possibility. What do you get when
you check binds status after you initially started it?

Out of the box it won't be doing much, that's for sure.



Cheers,
Tink

when checking the status of named I get the following:

[root@localhost jeremy]# service named status
version: 9.6.1-P2-RedHat-9.6.1-13.P2.fc12
CPUs found: 1
worker threads: 1
number of zones: 15
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
named (pid 1893) is running...

Thanks again for the help

Hmmm .. and when you connect to 53 from the local box?

yeah connects fine from the localhost, just another machine won't connect.

And since I'm not very good with FC .. is SELinux enabled, do you
see anything in the logs pertaining to SE blocking network traffic?

But again: my suspicion is still on the HOST OS ;}



Cheers,
Tink

1 members found this post helpful.

good thinking.
I went ahead and disabled SElinux and rebooted, nothing changed.
quite a strange issue. Oh well maybe it is something to do with the Host being Windows 7.
I disabled the firewall on Windows to see if anything changed, but no still can't connect.

Oh well, Thanks for the help Tinkster, a big blue thumbs up thank you for you!

Pleasure mate.

Sorry we didn't get the issue resolved, though! :/ Hope you find some
resource that gets you going all the way.


Cheers,
Tink