Re: name resolution

Thanks. On Thu, May 1, 2014 at 7:33 PM, filip wrote: > On Thu, 1 May 2014 12:48:47 +0530 > L V Gandhi wrote: > > > Resolving www.nse-india.com... failed: Name or service not known. > > wget: unable to resolve host address `www.nse-india.com' > > If you have the dnsutils package installed in th

Re: name resolution

On Thu, May 01, 2014 at 12:48:47PM +0530, L V Gandhi wrote: > I have name resolution problem in my debian virtual machine. > In my host operating system name resolution is ok. > Even in debian, ping works. But wget says resolution error as follows. > lvgandhi@lvgacersqueeze:~$ ping -c4 www.nse-indi

Re: name resolution

On Thu, 1 May 2014 12:48:47 +0530 L V Gandhi wrote: > Resolving www.nse-india.com... failed: Name or service not known. > wget: unable to resolve host address `www.nse-india.com' If you have the dnsutils package installed in the virtual machine, try looking up the name with dig. Look in /etc/res

Re: name resolution

On 01/05/14 08:18, L V Gandhi wrote: I have name resolution problem in my debian virtual machine. In my host operating system name resolution is ok. Even in debian, ping works. But wget says resolution error as follows. lvgandhi@lvgacersqueeze:~$ ping -c4 www.nse-india.com

Re: name resolution

On Thu, May 01, 2014 at 12:48:47PM +0530, L V Gandhi wrote: >I have name resolution problem in my debian virtual machine. >In my host operating system name resolution is ok. >Even in debian, ping works. But wget says resolution error as follows. >lvgandhi@lvgacersqueeze:~$ ping -c4

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

On Wed, February 24, 2010 1:59:48 PM +0530, Camaleón wrote: >On Tue, 23 Feb 2010 19:58:07 -0800, Hemanth M. C. wrote: > >> On Tue, February 23, 2010 21:30:51 +0530, Camaleón wrote: >> >> >>>Does this help? >>> >>>WGET can’t resolve host >>>http://serverfault.com/questions/76421/wget-cant-resolve

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

Camaleón schreef: On Tue, 23 Feb 2010 19:58:07 -0800, Hemanth M. C. wrote: ... As you are using the router's DNS facility, is up to the device performing such operation. Another thing you can try is by using your ISP's own DNS servers, instead the router's ones and see if you get different r

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

On Tue, 23 Feb 2010 19:58:07 -0800, Hemanth M. C. wrote: > On Tue, February 23, 2010 21:30:51 +0530, Camaleón wrote: > > >>Does this help? >> >>WGET can’t resolve host >>http://serverfault.com/questions/76421/wget-cant-resolve-host > > The solution mentioned in the link does not work for me, si

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

On Tue, 23 Feb 2010 19:58:07 -0800 (PST) "Hemanth M. C." wrote: ... > In short, pinging a certain destination helps the getent and wget commands > resolve the name correctly. Why is this so? Are the DNS lookups cached > somewhere? Does this cache have to be cleared? I don't know the solution

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

Camaleón, Thank you for replying to my mail. My replies inline... On Tue, February 23, 2010 21:30:51 +0530, Camaleón wrote: > >On Tue, 23 Feb 2010 00:30:15 -0800, Hemanth M. C. wrote: > >> I am facing a rather peculiar issue. I installed Debian 5.0.4 on my >> laptop. The basic network connectiv

Re: Name Resolution Issue from Browser only, on Debian 5.0.4

On Tue, 23 Feb 2010 00:30:15 -0800, Hemanth M. C. wrote: > I am facing a rather peculiar issue. I installed Debian 5.0.4 on my > laptop. The basic network connectivity works fine, and the DHCP client > daemon seems to have picked up the right config info from my DSL router. > But, anything related

Re: Name resolution on Debian/Windows network

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 21, 2003 at 04:07:29AM +0200, Micha Feigin wrote: > 127.0.0.1 is a reserved IP always pointing to the local computer. You > could even do ping 127.0.0.1 on you windows machines to ping themselves > (another way is to use the reserved name l

Re: Name resolution on Debian/Windows network

On Sat, Dec 20, 2003 at 02:58:52PM -0700, Jeffrey Barish wrote: > Jeffrey Barish wrote: > > > I have 3 computers on my home network. The Windows machines are > > connected to each other using ICS. I can ping one Windows machine > > from another Windows machine simply by naming the destination: >

Re: Name resolution on Debian/Windows network

Jeffrey Barish wrote: > I have 3 computers on my home network. The Windows machines are > connected to each other using ICS. I can ping one Windows machine > from another Windows machine simply by naming the destination: > > ping windowsB > > from machine windowsA will elicit a response. I ca

Re: Name resolution on Debian/Windows network

On (20/12/03 10:01), John Smith wrote: > On Fri, 2003-12-19 at 23:01, Jeffrey Barish wrote: > > I have 3 computers on my home network. The Windows machines are > > connected to each other using ICS. I can ping one Windows machine from > > another Windows machine simply by naming the destination:

Re: Name resolution on Debian/Windows network

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Dec 20, 2003 at 10:01:39AM +0100, John Smith wrote: > Try filling > the /etc/hosts file on your linux machine. Or set up your own bind. This actually really helps if you have a network behind a modem, since you don't have to wait for cached l

Re: Name resolution on Debian/Windows network

On Fri, 2003-12-19 at 23:01, Jeffrey Barish wrote: > I have 3 computers on my home network. The Windows machines are > connected to each other using ICS. I can ping one Windows machine from > another Windows machine simply by naming the destination: > > ping windowsB > > from machine windowsA w

Re: Name resolution on Debian/Windows network

Jeffrey Barish wrote: Haim Ashkenazi wrote: Jeffrey Barish wrote: I have 3 computers on my home network. The Windows machines are connected to each other using ICS. I can ping one Windows machine from another Windows machine simply by naming the destination: ping windowsB from machine

Re: Name resolution on Debian/Windows network

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Dec 19, 2003 at 10:28:40PM -0700, Jeffrey Barish wrote: > Clearly, some > software somewhere in Windows-land is resolving the names for the > Windows machines. Why doesn't it do the same for the Linux machine? It's using NetBIOS name resoluti

Re: Name resolution on Debian/Windows network

Monique Y. Herman wrote: > On Fri, 19 Dec 2003 at 22:01 GMT, Jeffrey Barish penned: >> I have 3 computers on my home network. The Windows machines are >> connected to each other using ICS. I can ping one Windows machine >> from another Windows machine simply by naming the destination: >> >> pin

Re: Name resolution on Debian/Windows network

Haim Ashkenazi wrote: > Jeffrey Barish wrote: > >> I have 3 computers on my home network. The Windows machines are >> connected to each other using ICS. I can ping one Windows machine >> from another Windows machine simply by naming the destination: >> >> ping windowsB >> >> from machine wind

Re: Name resolution on Debian/Windows network

Jeffrey Barish wrote: > I have 3 computers on my home network. The Windows machines are > connected to each other using ICS. I can ping one Windows machine from > another Windows machine simply by naming the destination: > > ping windowsB > > from machine windowsA will elicit a response. I ca

Re: Name resolution on Debian/Windows network

On Fri, 19 Dec 2003 at 22:01 GMT, Jeffrey Barish penned: > I have 3 computers on my home network. The Windows machines are > connected to each other using ICS. I can ping one Windows machine > from another Windows machine simply by naming the destination: > > ping windowsB > > from machine wind

RE: Name resolution on a dual homed host - Solved

] [mailto:[EMAIL PROTECTED] Behalf Of Stephen Patterson Sent: Monday, August 11, 2003 4:44 AM To: [EMAIL PROTECTED] Subject: Re: Name resolution on a dual homed host On Sun, 10 Aug 2003 22:20:10 +0200, John M. Purser wrote: > I've got a Debian woody box acting as firewall for a small home

Re: Name resolution on a dual homed host

On Sun, 10 Aug 2003 22:20:10 +0200, John M. Purser wrote: > I've got a Debian woody box acting as firewall for a small home network. It > has two ethernet cards with the internal network one being static and the > external one configured by DHCP. I use a cable modem for internet > connectivity.

Re: Name resolution on internal network

Richard Kimber said: > On Mon, 14 Oct 2002 21:31:27 -0600 > [EMAIL PROTECTED] (Bob Proulx) wrote: > >> And apparently a poor guess one at that. Just a few messages down in >> the list, seen in the archive here, the problem has been reported as >> being a Win2k DHCP server. > > I have this - my Ne

Re: Name resolution on internal network

On Mon, 14 Oct 2002 21:31:27 -0600 [EMAIL PROTECTED] (Bob Proulx) wrote: > And apparently a poor guess one at that. Just a few messages down in > the list, seen in the archive here, the problem has been reported as > being a Win2k DHCP server. I have this - my Netgear router seems to be configu

Re: Name resolution on internal network

On Mon, Oct 14, 2002 at 08:19:48PM -0700, nate wrote: > Alex Malinovich said: > > > I just checked it and that was it as it turns out. Interestingly enough, > > the problem was not that the search line was missing, but that it had > > \000 appended to the end of it. Since his was the first comput

Re: Name resolution on internal network

Bob Proulx <[EMAIL PROTECTED]> [2002-10-14 21:11:31 -0600]: > Alex Malinovich <[EMAIL PROTECTED]> [2002-10-14 03:32:08 -0500]: > > I just checked it and that was it as it turns out. Interestingly enough, > > the problem was not that the search line was missing, but that it had > > \000 appended to

Re: Name resolution on internal network

Alex Malinovich said: > I just checked it and that was it as it turns out. Interestingly enough, > the problem was not that the search line was missing, but that it had > \000 appended to the end of it. Since his was the first computer that I sounds like you may have a win32 DHCP server? or perh

Re: Name resolution on internal network

Alex Malinovich <[EMAIL PROTECTED]> [2002-10-14 03:32:08 -0500]: > On Mon, 2002-10-14 at 03:23, Leo Spalteholz wrote: > > Alex Malinovich <[EMAIL PROTECTED]> wrote: > > do you have a search line in the resolv.conf? > > search theloveshack.local > > I just checked it and that was it as it turns ou

Re: Name resolution on internal network

On Monday 14 October 2002 12:51 am, Alex Malinovich wrote: > I just helped my roommate set up Debian on his new computer and > everything is working just fine. Installed using the Woody installer and > immediately updated to the unstable packages. (He likes cutting edge. I > like bleeding edge exp

Re: Name resolution on internal network

On Mon, 2002-10-14 at 03:23, Leo Spalteholz wrote: > On 14 Oct 2002 02:51:27 -0500 > Alex Malinovich <[EMAIL PROTECTED]> wrote: > > > Unfortunately, his computer always wants a FQDN for all computers. So, > > whereas I can do an 'ssh gandalf' to connect to my mailserver, he has to > > use 'ssh ga

Re: Name resolution on internal network

On 14 Oct 2002 02:51:27 -0500 Alex Malinovich <[EMAIL PROTECTED]> wrote: > Unfortunately, his computer always wants a FQDN for all computers. So, > whereas I can do an 'ssh gandalf' to connect to my mailserver, he has to > use 'ssh gandalf.theloveshack.local'. I'm sure that there's some very > si

Re: Name resolution from Windows network

Quoting Moore, Paul ([EMAIL PROTECTED]): ... > I have absolutely no influence > over the site network setup, and even if I did, I'd never get anything > changed for the sake of Linux :-( ... > Fixed-IP machines have DNS names, so I can resolve their names by the usual > means (ping machinename, and

RE: name resolution

ser Cc: The recipient's address is unknown. Subject: Re: name resolution Ying Sun: I do not know why you need to remove the /etc/resolv.con file, but I think HP has a file called nsswitch.conf that you may need to modify a line in. In the /etc/nsswitch.conf file, make sure the line that s

Re: name resolution

Ying Sun: I do not know why you need to remove the /etc/resolv.con file, but I think HP has a file called nsswitch.conf that you may need to modify a line in. In the /etc/nsswitch.conf file, make sure the line that says hosts looks like this: hosts:filesdns This will make it look to th