Problematic DNS configuration with Open Suse 11

I have a experimental, custom build blade server, with 600 MHz VIA Epia and solid state disk. There is Latest OpenSuse 11 with all updates.

My intention is to use it as DNS server for a small, heterogeneous test network with linux and Windows clients.

The machines get their ip:s from DHCP server, but each ip address is bound to the NIC’s MAC and they are practically fixed ip addresses.

For some reason I can’t have the DNS server work in the intra net. I have filtered away firewall problems and the machines ping just as they should. I have no ACL’s and just the intra nets zone, no NS records, no MX recors neither. SOA settings ara a little bit obscure to me. If messing with SOA could be the source of the problem, I’d like to hear the explanation. I have tried with in-addr.arpa and without it, but it doesnt seem to help.

The problem can be found by pinging the machine’s name (like ping directory) or by dig (dig directory). To put it simply - I can’t connect the name of the computer to it’s ip-address, but ping with ip works.
I

Did you try adding in the IP addresses and host names to the host file? /etc/host

John

mppulkk wrote:

>
> I have a experimental, custom build blade server, with 600 MHz VIA Epia
> and solid state disk. There is Latest OpenSuse 11 with all updates.
>
> My intention is to use it as DNS server for a small, heterogeneous test
> network with linux and Windows clients.
>
> The machines get their ip:s from DHCP server, but each ip address is
> bound to the NIC’s MAC and they are practically fixed ip addresses.
>
> For some reason I can’t have the DNS server work in the intra net. I
> have filtered away firewall problems and the machines ping just as they
> should. I have no ACL’s and just the intra nets zone, no NS records, no
> MX recors neither. SOA settings ara a little bit obscure to me. If
> messing with SOA could be the source of the problem, I’d like to hear
> the explanation. I have tried with in-addr.arpa and without it, but it
> doesnt seem to help.
>
> The problem can be found by pinging the machine’s name (like ping
> directory) or by dig (dig directory). To put it simply - I can’t connect
> the name of the computer to it’s ip-address, but ping with ip works.
> I
>
>
mppulkk;

How are you setting up your zones? Are these static or dynamic? What kind of
result do you get from:
nslookup <host name>
Does this return an IP for the host?

If not then the error would seem to be in /etc/named.conf or perhaps the zone
file(s). It might help if you posted these concealing any sensitive entry with
dummy values.

If you are using static zones be sure you have the trailing periods correct.

If these are dynamic zones, do you see them in /var/lib/named/dyn and do they
contain correct information?

Just for your information DNS under Susie, when configured properly, works fine
for an intra net with either static or dynamic zones.

P. V.
Cogito cogito ergo cogito sum.

PV wrote:

> mppulkk wrote:
>
<snip>
>>
> mppulkk;
>
> How are you setting up your zones? Are these static or dynamic? What kind of
> result do you get from:
> nslookup <host name>
> Does this return an IP for the host?
>
> If not then the error would seem to be in /etc/named.conf or perhaps the zone
> file(s). It might help if you posted these concealing any sensitive entry
> with dummy values.
>
> If you are using static zones be sure you have the trailing periods correct.
>
> If these are dynamic zones, do you see them in /var/lib/named/dyn and do they
> contain correct information?
>
> Just for your information DNS under Susie, when configured properly, works
> fine for an intra net with either static or dynamic zones.
Also verify that named is running.

What is the result of “ps -A | grep named”

P. V.
Cogito cogito ergo cogito sum.

Actually I try to avoid /etc/host file. Perhaps I have misunderstood something, but I think that you don’t have to use /etc/host file with DNS. I did everything with the tools of the YAST2.

Finally I gave up and used my firewal’s DNS service.