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

Re: finding the ip address for dns, nslookup & etc.

Alan Chandler wrote:

On 08/08/10 20:14, peasthope@shaw.ca wrote:

I have a Debian router with dnsmasq working.
It connects to the ISP with DHCP.  What is the
standard way to find the ip address or addresses,
which dnsmasq is using for upstream nameservers?
Here are some things which don't help.

joule:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) 
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search pi.shawcable.net
joule:~# nslookup pi.shawcable.net
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
*** Can't find pi.shawcable.net: No answer




I am not sure I fully understand your question. However
dhclient, when it gets given a dhcp address will setup /etc/resolv.conf to point to the upstream nameservers. At least that is what happens with me. So I have both 127.0.0.1 but also the upstream nameservers in my /etc/resolv.conf
I am behind a 2wire gateway that comes with the Telmex Infinitum subscription, and my /etc/resolv.conf reads: 

hugo@debian:/etc$ more resolv.conf
domain gateway.2wire.net
search gateway.2wire.net
nameserver 192.168.1.254

and ifconfig reads partially:

wlan0     Link encap:Ethernet  HWaddr 00:14:a4:4c:3c:d5
          inet addr:192.168.1.194  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:a4ff:fe4c:3cd5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12867 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12702 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15905344 (15.1 MiB)  TX bytes:1088705 (1.0 MiB)

So does that mean that the gateway acts as a nameserver?
I still have quite a lot to learn about gateways ;-) and it all worked out of the box... 

Hugo
Reply to: