(I should have written my E-mail complete before sending it! sorry!) traceroute normally reverse-lookups names, as does host -a. Traceroute: # traceroute 192.168.1.102 traceroute to 192.168.1.102 (192.168.1.102), 30 hops max, 40 byte packets 1 192.168.1.102 (192.168.1.102) 1 ms 1 ms 0 ms ..it should have displayed my name: icarus.hafnet.nl host -a: # host -a 192.168.1.102 rcode = 0 (Success), ancount=1 102.1.168.192.IN-ADDR.ARPA 38400 IN PTR icarus.hafnet.nl For authoritative answers, see: 1.168.192.in-addr.arpa 38400 IN NS xtreme1 He DOES find my hostname with host -a, but complains about something? Traceroute fails... Strange thing is, it still works from my client: M$-DOS>tracert 195.81.35.224 Tracing route to guldennet.nl [195.81.35.224] over a maximum of 30 hops: 1 1 ms <10 ms <10 ms xtreme1.hafnet.nl [192.168.1.103] 2 28 ms 24 ms 24 ms xxxxxxxxx.xxxxxxxxx.xxxxxx.xx [000.000.000.000] 3 28 ms 26 ms 30 ms xxxxx.xxxxxxxx.xx [000.000.000.000] ..etc My suspicions pointed me to my /etc/resolv.conf, but that's correctly configured I'd say. Am I wrong? To make this mail even longer, here are the forward- and reverse zonefiles: Reverse: 1.168.192.in-addr.arpa. IN SOA xtreme1. icarus.guldennet.nl. ( 2000032300 10800 3600 632000 38400 ) 1.168.192.in-addr.arpa. IN NS xtreme1. 103.1.168.192.in-addr.arpa. IN PTR xtreme1.hafnet.nl. 102.1.168.192.in-addr.arpa. IN PTR icarus.hafnet.nl. 101.1.168.192.in-addr.arpa. IN PTR ineke.hafnet.nl. Forward: hafnet.nl. IN SOA xtreme1. icarus.guldennet.nl. ( 2000032300 10800 3600 632000 38400 ) hafnet.nl. IN NS xtreme1. xtreme1.hafnet.nl. IN A 192.168.1.103 icarus.hafnet.nl. IN A 192.168.1.102 ineke.hafnet.nl. IN A 192.168.1.101 mail.hafnet.nl. IN MX 50 xtreme1 www.hafnet.nl. IN CNAME xtreme1 ftp.hafnet.nl. IN CNAME xtreme1 proxy.hafnet.nl. IN CNAME xtreme1 Thanks, Rogier Rogier Maas wrote:

Hi,

I have made two master-zones in my BIND8 configuration. One forward, one reverse lookup zone. I've put this in my resolv.conf:

search mylocaldomain.com my-isps-domain.com nameserver 192.168.1.1 (that's the nameserver) nameserver 1.2.3.4 (nameserver of my isp)

I can traceroute through my 6.3-box and it displays the hostnames correctly, including the one of my box (not officially registered, the name is beeing returned by my nameserver).

Everything else is working perfectly for my clients. Forward AND reverse-lookups are always resolving. However, I still see "Connect from 192.168.1.2"-messages in my syslog, while those clients are clearly configured with a PTR-record, just like the linuxbox itself.

What am I doing wrong? I've made the same config over and over again. On another box it IS working, this is the only box that doesn't want to resolve names. Is it an oprion in inetd? Must I enable identd or something? Please help! ;-)

Thanks,

Rogier

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Hi. At 0:26 on 23 Mar 00, Rogier Maas begun to yabber about "[SLE] BIND8 issue" Date sent: Thu, 23 Mar 2000 00:26:52 +0100 From: Rogier Maas Send reply to: icarus@guldennet.nl Organization: Stichting Het GuldenNet - www.guldennet.nl To: SuSE Linux Mailing List Subject: [SLE] BIND8 issue

I have made two master-zones in my BIND8 configuration. One forward, one reverse lookup zone. I've put this in my resolv.conf:

search mylocaldomain.com my-isps-domain.com nameserver 192.168.1.1 (that's the nameserver) nameserver 1.2.3.4 (nameserver of my isp)

I can traceroute through my 6.3-box and it displays the hostnames correctly, including the one of my box (not officially registered, the name is beeing returned by my nameserver).

Everything else is working perfectly for my clients. Forward AND reverse-lookups are always resolving. However, I still see "Connect from 192.168.1.2"-messages in my syslog, while those clients are clearly configured with a PTR-record, just like the linuxbox itself.

What am I doing wrong? I've made the same config over and over again. On another box it IS working, this is the only box that doesn't want to resolve names. Is it an oprion in inetd? Must I enable identd or something? Please help! ;-)

As far as i know, inetd will only log client IP addresses.. I have reverse domains enabled on a network that i used to administer and there are no FQDN's loged in the syslogs.. Please correct me if i am wrong about this one :) Cya Matthew

Thanks,

Rogier

Matthew King: Network Engineer, Cable & Wireless Optus. My ICQ#: 2342475 Message me! Cellular Phone: +61 404 898544 040 489 8544 (Inside .au) Home e-mail: nerd@zip.com.au Work e-mail: Matthew.King@cwo.net.au Homepage: http://www.zip.com.au/~nerd/ -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d+ s: a--- C++++ UL++++ P+ L+++ E---- W++ N++ o++ K w O- M- V- PS+ PE Y+ PGP- t+ 5++++ X++ R+ tv++ b+++ DI+++++ D++ G+++ e* h* r++ y+ ------END GEEK CODE BLOCK------ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/