Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


   [Jerry Feldman:]
   Why can't your run a nameserver behind a linksys router? You can open up 
   the name service ports or you can declare one host as a dmz host.

The problem is NAT: you can open up port 53, and the nameserver can
respond to incoming requests, but when that response hits the
firewall, its return address doesn't get rewritten with the firewall's
address; thus, the host that issued the original request doesn't
realize it's gotten a response.

At least, that was my diagnosis when I was trying to run tinydns
behind a Linksys, and I think I tried every trick on the Web form
before giving up, buying a second hub, and putting the nameserver
outside the firewall.  Maybe more recent versions of the firmware fix
this problem, or maybe the four-port Linksys is smarter about this
than the one-port Linksys.

"Rav would never cross a bridge when an idolator was on it; he said, 'Maybe he
will be judged and I will be taken with him.'  Shmuel would only cross a
bridge when an idolator was on it; he said, 'Satan cannot rule two nations [at
once].'  Rabbi Yannai would examine [the bridge] and cross."  --Shabbat 32a
== Seth Gordon == sethg at == == std. disclaimer ==
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at (Subject line is ignored).

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /