[sudo-sys] our local network - how does it work?

[Marc Juul]

On Thu, May 16, 2013 at 8:28 PM, Yardena Cohen <yardenack at gmail.com> wrote:

> I'm trying to rename tamale.sudoroom.org to door.sudoroom.org. It
> already works fine from outside the space. From within the space,
> however:
>
>   tamale.sudoroom.org resolves to 192.168.1.2
>   door.sudoroom.org resolves to 50.0.83.116
>
> This means packets to "tamale" get through but packets to "door" just
> time out. I've already tried changing its hostname and rebooting, but
> I suspect that a local DNS server is involved here and that we need
> access to it.
>
> It looks like DNS is being served by the Cisco AP running dd-wrt at
> 192.168.1.49 - is that true?
>

Last I checked the DNS was on space.sudo

Check the bind config on that server. Should be what you want.

That's also where the .sudo domain exists.

-- 
Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sudoroom.org/pipermail/sudo-sys/attachments/20130517/fe26ee77/attachment.html>