| 1 |
Alan Mackenzie <acm@×××.de> writes: |
| 2 |
|
| 3 |
> Anyhow, it is surely not the router setup which is the problem - name |
| 4 |
> lookup works fine under my Debian sarge system. |
| 5 |
|
| 6 |
Is the sarge system pointed at the same router for default route? |
| 7 |
|
| 8 |
Show first line of /etc/hosts |
| 9 |
|
| 10 |
Show Sarge system /etc/resolv.conf and first line of /etc/hosts |
| 11 |
|
| 12 |
Surely your router has a `status' screen. It should show you current |
| 13 |
IP and DNS servers. |
| 14 |
|
| 15 |
Otherwise hit this page |
| 16 |
http://www.jtan.com/~reader/ |
| 17 |
to learn your outer IP address |
| 18 |
|
| 19 |
With that you can learn the nameservers for a domain... |
| 20 |
|
| 21 |
Sorry I can't remember which tool or arguments do this but it is |
| 22 |
possible to lookup a domain name and be shown the nameservers that |
| 23 |
serve that domain. Not sure if its nslookup, dig, whois or something |
| 24 |
else but maybe some kind soul will post the command and arguments that |
| 25 |
will retrieve that info. |
| 26 |
|
| 27 |
Once you've ascertained that actual outer nameserver. Put that in |
| 28 |
/etc/resolv.conf and see if it makes a difference. |
Archives