DNS Problems

imemyself · 02-12-2005, 04:15 PM

I'm having trouble with my SuSE 9.2 laptop and DNS. I can resolve domain names for external websites(llike lq, or slashdot, etc), but not domains on my local network(well, kind of). I have a DNS server running on a Red Hat machine that I have all my computers set to check DNS from(because I want to let users enter a domain name instead of an IP, like 192.168.2.16, and because I'm cheap ;) ). My DNS server is running at 192.168.2.16, and that is the first IP in /etc/resolv.conf. It is also shown in YAST's Network Devices thing. What is really odd, is that nslookup successfully gets the IP address for the domain names, and I can ping that IP(and even get the local website I'm hosting from that IP). However, I can't ping the domain name, and it does not work when I put it in the address bar of a browser(tried Firefox and Konqueror). In case it matters, I'm connecting to my network via wifi(802.11g with WPA). DNS works fine on XP on this laptop, and on an XP desktop(both set to 192.168.2.16 for DNS). DNS also works on the server that is running BIND(What I mean is that I can ping www.garrauxlin.local, and get responses). Here's what happens when I do nslookup and try to ping an IP/domain:

Code:

tsbl-suse-92:~ # nslookup plone.garrauxlin.local
Server:         192.168.2.16
Address:        192.168.2.16#53

Name:   plone.garrauxlin.local
Address: 192.168.2.12

tsbl-suse-92:~ # ping 192.168.2.12
PING 192.168.2.12 (192.168.2.12) 56(84) bytes of data.
64 bytes from 192.168.2.12: icmp_seq=1 ttl=64 time=4.25 ms
64 bytes from 192.168.2.12: icmp_seq=2 ttl=64 time=1.23 ms

--- 192.168.2.12 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.233/2.745/4.258/1.513 ms
tsbl-suse-92:~ # ping plone.garrauxlin.local
ping: unknown host plone.garrauxlin.local
tsbl-suse-92:~ #

I'm sure there's something really obvious that I'm forgetting or not doing, but I can't seem to get it to work. Any ideas?

aznluvsmc · 02-12-2005, 06:44 PM

Can you post the database for the forward zone lookup? Nslookup queries the reverse zone lookup database but when you try to ping a computer the client will query the forward zone lookup database.

You might also want to post the /etc/resolv.conf file for the client. Maybe you have a typo?

imemyself · 02-12-2005, 08:42 PM

OK, I'm not 100% sure what the forward zone lookup database would be, I usually take the lazy way and use webmin.

I think its this

Code:

$ttl 38400
garrauxlin.local.       IN      SOA     garrauxlin.local. root.garrauxlin.local. (
                        1105922850
                        10800
                        3600
                        604800
                        38400 )
garrauxlin.local.       IN      NS      ns
www.garrauxlin.local.   IN      A       192.168.2.16
mail.garrauxlin.local.  IN      A       192.168.2.15
java.garrauxlin.local.  IN      A       192.168.2.14
garrauxlin.local.       IN      A       192.168.2.16
ns.garrauxlin.local.    IN      A       192.168.2.16
192.168.2.13            IN      PTR     ns.garrauxlin.local
plone.garrauxlin.local. IN      A       192.168.2.12
garrauxlin.local.       IN      MX      1 mail.garrauxlin.local
asp.garrauxlin.local.   IN      A       192.168.2.9
192.168.2.12            IN      PTR     plone.garrauxlin.local
192.168.2.16            IN      PTR     garrauxlin.local

though, right?

And the resolv.conf on the SuSE client looks like:

Code:

domain garrauxlin.local
nameserver 192.168.2.16

aznluvsmc · 02-12-2005, 09:00 PM

This zone file seems to have the both forward zone entries and reverse zone entries in them. I wonder how the PTR records got in there if this is a forward lookup zone. I assume you didn't put them in yourself. Reverse zone entries are the PTR records which map IP addresses to host names.

Anyways try making it look like this.

$ttl 38400
@ IN SOA ns.garrauxlin.local. root.garrauxlin.local. (
1105922850
10800
3600
604800
38400 )
IN NS ns.garrauxlin.local.
www.garrauxlin.local. IN A 192.168.2.16
mail.garrauxlin.local. IN A 192.168.2.15
java.garrauxlin.local. IN A 192.168.2.14
garrauxlin.local. IN A 192.168.2.16
ns.garrauxlin.local. IN A 192.168.2.16
192.168.2.13 IN PTR ns.garrauxlin.local
plone.garrauxlin.local. IN A 192.168.2.12
garrauxlin.local. IN MX 1 mail.garrauxlin.local
asp.garrauxlin.local. IN A 192.168.2.9
192.168.2.12 IN PTR plone.garrauxlin.local
192.168.2.16 IN PTR garrauxlin.local

The resolv.conf file looks correct.

aznluvsmc · 02-12-2005, 11:30 PM

Hey,

I'm actually testing DNS right now on Fedora Core 3 and it doesn't work. I think it's some kind of default configuration with Red Hat's distro that's causing the problem. Supposedly, it's setup for a caching only server but I don't see how that is so as the configuration looks fine to me. To be sure it wasn't what I was doing, I did the same procedure on my SuSE and it worked fine so I know Red Hat did something with the DNS.

imemyself · 02-15-2005, 06:35 PM

I changed the lookup thing to like you suggested, and SuSE still doesn't work. I don't think that its too serious of a DNS problem as my Windows machines access it fine. The DNS server is running on RHEL 4 beta(nahant). And even though its a beta it actually runs pretty well. I really appreciate your help.

aznluvsmc · 02-16-2005, 08:48 PM

Actually, taking another look at your /etc/resolv.conf file. It's actually incorrect. I guess I didn't look closely enough. You need to add a search line so that the file now looks like:

Code:

domain garrauxlin.local
search garrauxlin.local
nameserver 192.168.2.16

The search line tells the SuSE laptop to append that domain name to any non-FQDN specified host names. Without it, it wouldn't know which domain to request the host lookup from.

Forget what I said about the DNS not working. I found out that the location I placed my zone files was not correct as they had to be a few levels down the folder tree and then be symbolically linked back up to where I initially put them.

imemyself · 02-16-2005, 09:31 PM

lol, I added that and it still doesn't work. I wonder if Novell could be any help in this. I guess its not a huge deal, I could always add the few domains to by /etc/hosts file, but it would be nice if DNS would work. Its weird that external domains also work(though the local DNS server I presume, but local ones don't.

aznluvsmc · 02-16-2005, 09:57 PM

Hmm..... I must say, I'm completely stumped on this one.

tonkajeep34 · 03-04-2005, 04:28 PM

Have you guys heard anymore about this? It's been a sort of anoyance that'd i'd like to fix also.

Thanks,
Mike

imemyself · 03-10-2005, 09:37 AM

Not really, I was going to ask about it on Novell's message board but never got around to it.

imemyself · 05-31-2005, 08:43 PM

If anyone's still wondering about this, I posted on usenet(alt.os.linux.suse), and someone told me where to find a fix for this:

http://groups-beta.google.com/group/...76ab9dc099b760

Quote:

Serg wrote:
>>Chris Cox wrote:
>>Question has already been answered once in the other
>>group. The reason is that .local is a reserved
>>top level domain for multicast traffic ONLY. As such,
>>SUSE 9.2 and SLES9 (and SUSE 9.1 with the latest YOU
>>update) will only try to access a host that ends
>>in .local via multicast.

> Thank you for answer.
> But what can i do fo resolver this without change domain name ??

> Serg

I mistook you for a prior post with the name Serg (small world).

# cd /lib
# ln libresolv.so.2 libresolv.so.2-orig
# rm libresolv.so.2
# cp libresolv.so.2-orig libresolv.so.2
# perl -pi -e 's/local/lozal/g' libresolv.so.2

You'll probably want to reboot after this.

Chris Cox Apr 22, 3:59 pm show options
Newsgroups: novell.support.suse.linux.enterprise-server
From: Chris Cox <notc...@notairmail.net> - Find messages by this author
Date: Fri, 22 Apr 2005 19:59:48 GMT
Local: Fri,Apr 22 2005 3:59 pm
Subject: Re: sles9 and PING and local DNS = Problem !!!!!
Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse

- Hide quoted text -
- Show quoted text -
Chris Cox wrote:
> Serg wrote:

>>> Chris Cox wrote:
>>> Question has already been answered once in the other
>>> group. The reason is that .local is a reserved
>>> top level domain for multicast traffic ONLY. As such,
>>> SUSE 9.2 and SLES9 (and SUSE 9.1 with the latest YOU
>>> update) will only try to access a host that ends
>>> in .local via multicast.

>> Thank you for answer.
>> But what can i do fo resolver this without change domain name ??

>> Serg

> I mistook you for a prior post with the name Serg (small world).

> # cd /lib
> # ln libresolv.so.2 libresolv.so.2-orig
> # rm libresolv.so.2
> # cp libresolv.so.2-orig libresolv.so.2
> # perl -pi -e 's/local/lozal/g' libresolv.so.2

> You'll probably want to reboot after this.

There's an update in SLES9 SP1 that fixes this problem without
having to edit the resolv library: