BIND 9 Help

shane200_ · 07-04-2006, 04:47 PM

I have setup bind on my server, I have a Wireless LAN and wired LAN, I have a cisco 2600 router doing routing between subnet, when I am on the wired LAN I can ping my servers by IP and host name but when I am on the Wireless LAN I can only ping by IP and not host name, can any one tell me y this is happen?

musicman_ace · 07-04-2006, 06:15 PM

what does your /etc/resolv.conf look like on a wireless client?

shane200_ · 07-05-2006, 09:59 AM

In that file I just see

/etc/resolv.conf

search Domain_name.local
domain Domain_name.local
nameserver 192.168.190.4 => this is the IP for the DNS server

so what should I do for the wireless side which is 192.168.180.0? what should I do in this file so I can ping the IP and Host name from the wireless side of my network?

ARC1450 · 07-05-2006, 11:35 AM

I assume you have the Cisco router properly routing between subnets, correct?

sgarci · 07-05-2006, 01:14 PM

There 3 things that you could do:

Copy the named.conf file from the wired zone to the wireless zone.

OR

Setup a slave name server within the wireless zone to pull zone data from the master zone.

OR

If your network is not large try manually to edit /etc/hosts file in both LANs

I hope this will help

Thanks

ARC1450 · 07-05-2006, 02:06 PM

Why go to all that trouble? Just specify a route in the router to go from one network to the other as doing all of that is way too much trouble.

gizza23 · 07-05-2006, 02:18 PM

Assuming you have at least two different networks assigned for the WLAN and LAN there should be two DHCP servers or manually assigned network information for both NICs. I would like to know if your wireless NIC has a default gateway set up. If it has a default gateway what DNS server is it querying?

What does this give you?

Code:

nslookup [computer name] [DNS IP]

JimBass · 07-05-2006, 09:43 PM

You most likely don't have BIND configured with individual host names. Chances are that when you say you can ping by name from the wired LAN but not the wireless LAN, you aren't having a DNS issue, but rather a windows network issue.

If the name you are looking for is a FQDN (fully qualified domain name), something like server1.domain.com, and it doesn't know, that is DNS. If you are looking for a name like server1, then the problem isn't DNS, but rather that your Cisco isn't allowing the windows networking info to pass between wired and wireless subnets.

Peace,
JimBass