On 10/5/2010 3:49 PM, Dotan Cohen wrote:
On Tue, Oct 5, 2010 at 20:30, Eivind Olsen<eiv...@aminor.no> wrote:
However, another site that _does_ work (with both nameservers on this
host, not just ns1) shows the same thing:
# nslookup ns1.sharingserver.eu 178.63.65.136
Server: 178.63.65.136
Address: 178.63.65.136#53
** server can't find ns1.sharingserver.eu: NXDOMAIN
How do you mean this one is working? It's working just as badly as your
first example.
Yes, but typing the domain into Firefox brings up the webpage that
I've put on that server!
You're introducing a bunch of other variables when you use a browser to
troubleshoot a DNS resolution problem:
1) The browser might have cached the DNS response
2) The browser might have cached the web content itself and not be
performing DNS lookups
3) The browser might be using a PAC (proxy auto-config) file which
shuffles the request off to some proxy
I would suggest sticking to DNS troubleshooting tools to troubleshoot
DNS. And dig/host is to be greatly preferred for that purpose over
nslookup, which sucks in more ways than I care to list here.
- Kevin
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
