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]

Old school DNS question



On Fri, Apr 1, 2011 at 2:52 PM, Kurt Keville <kkeville-3s7WtUTddSA at public.gmane.org> wrote:

> We have a bunch of nodes that hit a particular DNS server and while we can
> see that name service is running on that server, our queries do not
> resolve.
> Is there some remote way to find out if they are blocking addresses or
> something like that? We don't have access to the server so checking their
> logs is not an option.
>


The dig command is very useful for testing DNS queries. See the man page for
all the things it can do, but for simple checks, just invoke it with a
domain name argument.

Pair that with Wireshark, which is a tool that enables you to watch network
traffic on your LAN (or at least traffic moving through your network
interface). To filter out all but the DNS queries and responses, set the
capture filter string to "port 53" in the capture interface options screen.





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 / webmaster@blu.org