DNS lookup fails connecting to server on same network
Ryan Rix
phrkonaleash at gmail.com
Wed Nov 5 21:07:27 MST 2008
Hi,
There is something definitely wrong with both of these dns servers, or my
router is just plain stupid:
The nameservers that act oddly are
#nameserver 63.208.196.113
#nameserver 63.208.196.114
note they are commented out :) It works like this.
Now, if I do ANY nslookup on these nameservers:
rrix at wanton:~$ nslookup google.com 63.208.196.113
Server: 63.208.196.113
Address: 63.208.196.113#53
** server can't find google.com.phnx.qwest.net: REFUSED
Why in God's name it does this is beyond me. qwest.net has a dns server in
their help documents that I may be able to use:
http://www.qwest.net/help/roaming.html
rrix at wanton:~$ nslookup google.com 205.171.3.65
Server: 205.171.3.65
Address: 205.171.3.65#53
Non-authoritative answer:
Name: google.com
Address: 209.85.171.99
Name: google.com
Address: 72.14.207.99
Name: google.com
Address: 64.233.187.99
rrix at wanton:~$ nslookup wanton.dyndns.org 205.171.3.65
Server: 205.171.3.65
Address: 205.171.3.65#53
Non-authoritative answer:
Name: wanton.dyndns.org
Address: 204.193.209.193
But honestly NONE of this makes any sense! The 'bad' nameservers are used by
my router, and /it/ has no problem at all connecting to the dingdang
server... I don't know what is going on. I'll just play with resolv.conf. If
I can find the setting to disable autowriting the /etc/resolve.conf, I can
just rewire the linksys at my father's house to 192.168.0.1 and just have a
static resolv.conf, which sucks if I ever wish to use a friend's/library's
network but honestly, that is rare, and I can just reverse the dhclient arg
and rerun /etc/init.d/networking.
This is probably all my fault. I have hacked this thing's networking up so
badly trying to get wireless working, first under ndiswrapper then natively
with the rtl8180 drivers, I'm not really surprised things are this buggered
up.
~Ryan
On Wed, Nov 5, 2008 at 6:40 PM, Dan Lund <situationalawareness at gmail.com>wrote:
> Well, it's been ages since I've touched a dlink router honestly, I
> believe there is a dhcp setting page inside of it's dns reference, but
> maybe I'm mistaking it for a belkin.
>
> Normally what happens is the DHCP portion of the router allocates DNS
> and IP information to the requesting DHCP client, and it uses it
> accordingly.
> As far as the settings on that router, I'm rather clueless since every
> one of them are different to a huge degree.
>
> Thanks,
> Dan Lund
>
> "There is only one good, namely knowledge, and only one evil, namely
> ignorance."
> --Socrates
>
>
>
> On Wed, Nov 5, 2008 at 6:11 PM, Ryan Rix <phrkonaleash at gmail.com> wrote:
> > Hi,
> >>I mean, you could edit the /etc/dhclient.conf
> > What could I add in there? is there anyway to trick the router into only
> > using itself as a DNS server? It is the one informing my computer of the
> DNS
> > servers, so shouldn't I be able to control who it refers to?
> >
> > ~Ryan
> >
> > On Tue, Nov 4, 2008 at 3:44 PM, Dan Lund <situationalawareness at gmail.com
> >
> > wrote:
> >>
> >> The file shouldn't update on reboot, it should only update when
> >> dhclient (or whatever DHCP client style is used in your distro) snags
> >> an IP and DNS information from the DHCP server. Pretty much that's
> >> what determines what goes into the /etc/resolv.conf.
> >>
> >> I mean, you could edit the /etc/dhclient.conf (again, assuming your
> >> using dhclient for DHCP initialization), or just edit the
> >> /etc/resolv.conf, toss it to ./etc/resolv.conf.saved and if it goes
> >> fubar then copy the /etc/resolv.conf.saved to /etc/resolv.conf.
> >> (VERY ad-hoc and amateur but a quick fix)
> >>
> >> In theory though, you should be able to bounce between DHCP address
> >> changes network to network without a problem. This is the exception
> >> because DHCP update is causing a problem somehow. The main culprit is
> >> probably one of the router's DNS server address allocations perhaps.
> >>
> >> Great I wait until the end of this then read your using Debian. hah...
> >> I forget how that works but if I remember right it uses dhcpcd...
> >>
> >> Thanks,
> >> Dan Lund
> >>
> >> If you need more than 3 levels of indentation, you're screwed anyway,
> >> and should fix your program.
> >> --Linus Torvalds, Original Inventor of the Linux kernel
> >> August, 2006
> >>
> >>
> >>
> >> On Tue, Nov 4, 2008 at 5:59 AM, Ryan Rix <phrkonaleash at gmail.com>
> wrote:
> >> > Hi,
> >> >
> >> > I commented out the qwest dns servers, and it worked. but this file
> >> > updates at
> >> > reboot, no?
> >> > Also, about half the time I am behind a dlink router at my ftather's
> >> > house;
> >> > will this conflict now? if the resolv.conf is edited is it assumed to
> >> > stay
> >> > after reboot? The dlink's at 192.168.0.1 and the linksys is
> >> > 192.168.1.1....
> >> > is there any way to use both with one config file, or will it err?
> >> >
> >> > --
> >> > Thanks and best regards,
> >> > Ryan Rix
> >> > TamsPalm - The PalmOS Blog
> >> >
> >> > I support Debian GNU/Linux and KDE as the ultimate desktop
> environment.
> >> > Why don't you?
> >> >
> >> >
> >> >
> >> >
> >> > On Tue November 4 2008 12:33:11 am Dan Lund wrote:
> >> >> How about what's in your /etc/resolv.conf?
> >> >> maybe the /etc/nsswitch.conf just to make sure nothings odd?
> >> >> It's a start.
> >> >> even try appending a period/dot ( . ) after the name to denote it as
> a
> >> >> FQDN absolutely.
> >> >>
> >> >> Thanks,
> >> >> Dan Lund
> >> >>
> >> >> If you need more than 3 levels of indentation, you're screwed anyway,
> >> >> and should fix your program.
> >> >> --Linus Torvalds, Original Inventor of the Linux kernel
> >> >> August, 2006
> >> >>
> >> >> On Mon, Nov 3, 2008 at 10:09 PM, Ryan Rix <phrkonaleash at gmail.com>
> >> >> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > I have recently configured a new Debian GNU/Linux server and
> migrated
> >> >> > the
> >> >> > settings and stuffs from my old laptopserver.
> >> >> >
> >> >> > Everything works shiningly, except for one thing: when I try to
> >> >> > access
> >> >> > the server via its fqdn, my laptop returns a DNS error, unknown
> host.
> >> >> >
> >> >> > I know that somewhere in the bowels of my laptop, only while
> >> >> > connected to
> >> >> > the same network as the server behind a dlink G router, it's
> >> >> > becoming
> >> >> > corrupted because:
> >> >> >
> >> >> > maylay:~# nslookup wanton.dyndns.org 205.171.2.65
> >> >> > Server: 205.171.2.65
> >> >> > Address: 205.171.2.65#53
> >> >> >
> >> >> > Non-authoritative answer:
> >> >> > Name: wanton.dyndns.org
> >> >> > Address: 204.193.219.193
> >> >> >
> >> >> > where 205.11.2.65 is the primary dns reported by the router. The
> >> >> > address
> >> >> > it pulls is valid, indeed.
> >> >> >
> >> >> > maylay:~# nslookup wanton.dyndns.org
> >> >> > Server: 192.168.0.1
> >> >> > Address: 192.168.0.1#53
> >> >> >
> >> >> > Non-authoritative answer:
> >> >> > Name: wanton.dyndns.org
> >> >> > Address: 204.193.219.193
> >> >> >
> >> >> > using the router for DNS reports the same IP address, leading me to
> >> >> > believe the laptop is corrupting or doing *SOMETHING* to prevent a
> >> >> > connection.
> >> >> >
> >> >> > My hosts file is clean:
> >> >> > 127.0.0.1 localhost
> >> >> >
> >> >> > I think that would be the only thing prohibiting a connection on
> the
> >> >> > laptop, so I honestly am at a loss of what to do.
> >> >> >
> >> >> > Any ideas are much appreciated.
> >> >> > ~Ryan
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Thanks and best regards,
> >> >> > Ryan Rix
> >> >> > TamsPalm - The PalmOS Blog
> >> >> >
> >> >> > "See, he's more dangerous during the off season"
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > ---------------------------------------------------
> >> >> > PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> >> >> > To subscribe, unsubscribe, or to change your mail settings:
> >> >> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >> >>
> >> >> ---------------------------------------------------
> >> >> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> >> >> To subscribe, unsubscribe, or to change your mail settings:
> >> >> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >> >
> >> >
> >> >
> >> > ---------------------------------------------------
> >> > PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> >> > To subscribe, unsubscribe, or to change your mail settings:
> >> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >> >
> >> ---------------------------------------------------
> >> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> >> To subscribe, unsubscribe, or to change your mail settings:
> >> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> >
> >
> > --
> > Thanks and best regards,
> > Ryan Rix
> > TamsPalm - The PalmOS Blog
> >
> >
> > Jasmine Bowden - Class of 2009, Marc Rasmussen - Class of 2008, Erica
> > Sheffey - Class of 2009, Rest in peace.
> >
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
--
Thanks and best regards,
Ryan Rix
TamsPalm - The PalmOS Blog
Jasmine Bowden - Class of 2009, Marc Rasmussen - Class of 2008, Erica
Sheffey - Class of 2009, Rest in peace.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20081105/380e1784/attachment.htm
More information about the PLUG-discuss
mailing list