[ previous ] [ next ] [ threads ]
 From:  Aaron <lists at mycommunitynet dot net>
 To:  "'m0n0wall'" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  DNS forwarder & OS X Printer Sharing over PPTP
 Date:  Thu, 16 Sep 2004 23:45:48 -0700
I am having trouble getting the DNS forwarder to work. I'm not sure if 
it is something that is the result of m0n0wall or my machine(s) running 
MacOS 10.3.5. What I am trying to do it print to shared USB printers 
via the built in CUPS printer sharing over a PPTP connection. This does 
not normally work over the PPTP connection since OS X does the sharing 
using rendezvous. However by adding the IP of Adroit (the print 
"server") to the proper place in cups.conf, the printers show up over 
the PPTP connection. I ran into an issue though. When printing, the 
print dialogue was complaining that it could not resolve Adroit.local 
and nothing was printing.

My issue is this though. even though I have added Adroit.local (caps 
does matter I found) to the DNS forwarder, enabled the DNS forwarder 
and checked/unchecked (I tried both since it is a static IP) "register 
DHCP leases in DNS forwarder" AND added an override entry for Adroit, 
it does not work.

In General setup, the hostname is set to m0n0wall and domain set to 
local. Version is pb24r585.

$ dig Adroit.local

Adroit.Local.           0       IN      A

;; Query time: 96 msec
;; WHEN: Thu Sep 16 10:24:06 2004
;; MSG SIZE  rcvd: 46

Seems good...
$ ping Adroit.local
ping: unknown host Adroit.local
$ ping adroit.local
ping: unknown host Adroit.local

However I can ping the IP.

$ ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=63 time=79.342 ms
64 bytes from icmp_seq=1 ttl=63 time=81.284 ms

Huh, strange. I can add Adroit.local to my /etc/hosts file and ping now 

$ ping Adroit.local
PING Adroit.local ( 56 data bytes
64 bytes from icmp_seq=0 ttl=63 time=76.066 ms
64 bytes from icmp_seq=1 ttl=63 time=74.712 ms

However adding this to my hosts file is not ideal. Any suggestions on 
what I should do to get this working? I tried rebooting but this didn't 
solve my problem. I don't know what else to do.