1847249 Members
2865 Online
110263 Solutions
New Discussion

Re: telnet session

 
Linda Lux
Regular Advisor

Re: telnet session

my resolv.conf has
domain K460.americanid.com
nameserver 192.168.1.44
nameserver 10.6.2.52

when I do a nslookup it took 30 seconds
before this came up

# nslookup
*** Can't find server name for address 192.168.1.44: Non-existent domain
*** Can't find server name for address 10.6.2.52: Non-existent domain
*** Default servers are not available
Using /etc/hosts on: K460

If it isn't one thing, it's another
Linda Lux
Regular Advisor

Re: telnet session

Do I have to have a route added for these dns servers in my netstat -rn?
Linda
If it isn't one thing, it's another
Linda Lux
Regular Advisor

Re: telnet session

I am still having the delay, I sent the nslookup previously.
Thanks
If it isn't one thing, it's another
Robert-Jan Goossens
Honored Contributor

Re: telnet session

Linda,

Do you have a windows pc nearby ?

open a command box and enter ipconfig /all

look for the ipaddresses of your DNS servers. Are they different from the ones you use on your box ?

Robert-Jan

Linda Lux
Regular Advisor

Re: telnet session

I only get my PC configuration info
when I do this command
Linda
If it isn't one thing, it's another
Linda Lux
Regular Advisor

Re: telnet session

Sorry

I got this for the main DNS server
If it isn't one thing, it's another
Robert-Jan Goossens
Honored Contributor

Re: telnet session

DNS is correct, 192.168.1.44

domain K460.americanid.com --> kproducts.com

Is your domain name OK ?

Robert-Jan

Ps Linda Lux -> lin ux -->is it a coincidence :-)



Linda Lux
Regular Advisor

Re: telnet session

thats what I have had always before turning DNS on, it corresponds to the sendmail.cf
file
Linda

If it isn't one thing, it's another
Mel Burslan
Honored Contributor

Re: telnet session

Sorry, I forgot to check this thread yesterday.

Is there any other servers that you can run a successful nslookup command nearby ? If yes, could you please check what your dns server name shows up as, i.e., run the command

nslookup 192.168.1.44

if the response you got, has something other than americanid.com, this may be the cause of your headaches.

Right now, you machine presents itself to the other machines on the network as K460.americanid.com.

and I am not sure about the proper configuration of your DNS server right now because of the following:

mburslan@nomad:[/home/mburslan]
$ nslookup k460.americanid.com
Using /etc/hosts on: nomad

looking up FILES
Trying DNS
Non-authoritative answer:
Name: k460.americanid.com
Address: 192.168.1.5

also

mburslan@nomad:[/home/mburslan]
$ nslookup kproducts.com
Using /etc/hosts on: nomad

looking up FILES
Trying DNS
Non-authoritative answer:
Name: kproducts.com
Address: 192.168.1.5

this is actually obtained from my local hpux workstation. 192.168.x.y ip addresses are actually reserved for internal network use and never get advertised to the outside world. Whoever is managing the DNS servers for this domain, did not sound too competent to me, but I am no DNS admin, so I will not say anything further.

I am not sure about the nslookup capability form your win98 workstation but if you do not have such a tool, you can download this freeware application called hoverip

http://www.snapfiles.com/get/hoverip.html

and see if you can see this machine from the windows workstation via nslookup with both domain names, i.e., kproducts.com or americanid.com and if yes what ip address is being returned for these names.
________________________________
UNIX because I majored in cryptology...
Linda Lux
Regular Advisor

Re: telnet session

All of a sudden, everything is moving along great - do you suppose I will find out what the network people did?

Thanks for all your help
If it isn't one thing, it's another
Mel Burslan
Honored Contributor

Re: telnet session

In my past experiences, no offense to any network admins here, I have found many of the so-called "Network Experts" are usually doing their stuff by draw of the luck. If nobody complains, they mark what they have done is a good job and repeating it many times to "solve" same problems. And in the midlle of the smooth flow, if someone like you comes and tells them what they did broke the system, the first response you will hear "our networking is working fine, it must be the server" and they drag their feet forever and a day. Then comes along someone who really understands what (wrong) they did and and undoes it. But usually people like this, i.e. people who know what they are doing instead of experimenting on a slew of users, do not last long in this culture. So, beware :)

Out of my soapbox.

________________________________
UNIX because I majored in cryptology...