Slow telnet response after installing Bind

Dear all,

I have installed the Bind 9.2 in Redhat/Solaris box, it seems that after installing the Bind, the telentlogin response in between the client and the server (just installed primary domain) are very very slow.

1) I do not want to add the host name in /etc/hosts as I may have many ip address and they are all changeable.

2) I hear that we are play around with the named.conf

Here is the answer from perious people

1. Make sure that your box have correct setup with DNS server daemon program: named(bind 9.0)
2. Add your host name and IP address in file:" /etc/hosts" like:
      192.168.1.1         Myname
3. If you need to run DNS server on your machine, then you'd better add an item to the PTR file. About
details, you can look for DNS configrations on net.
4. If you need not to run the DNS server then just kill DNS daemon service: "killall named", and the
change the resolve file: "/etc/resolv.conf" delete all the nameserver lines.

I may have the answer from point 3

Thanks in advance

edmundliAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jlevieCommented:
It sounds like you may not be getting reverse lookups of the the  client IP's. You don't say whether the clients opening the telnet sessions are on the local network or if they are at random Internet addresses. If the clients are part of a local network that the DNS server is responsible for, the you simply need to add the appropriate A and PTR records for those clients. On the other hand, if the clients are at random on the Internet you need to figure out why your DNS server isn't resolving the hostnames from the client IP's. In some cases there won't be a DNS PTR record available and a timeout will occur, but in many cases there should be a record available. A simple check of your DNS server would be to lookup something that will have a PTR record and then see if you can lookup the hostname from that IP, say like:

chaos> host ftp.redhat.com
ftp.redhat.com. has address 216.148.218.201
ftp.redhat.com. has address 63.240.14.63
chaos> host 216.148.218.201
201.218.148.216.in-addr.arpa. domain name pointer ftp.redhat.com.

If you can't duplicate the above using your DNS server, then something isn't configured right.
0
edmundliAuthor Commented:
So you mean that they should have PTR record in DNS server in order to speed up the telent login seesion ?

If I have many ip addresses that I may not know, then they will have difficulity to login with acceptable time. ( I will in few seconds rather than 60-90 secs. )

Regards
0
jlevieCommented:
If this DNS server is one for a local network, then yes you need A & PTR records for all of the IP's that are in use on the local network. Any clients on the local network that aren't properly listed in the DNS will have problems with any of the IP services that do a reverse lookup of a connecting client's IP. And it's not just telnet that does that. Sendmail, imap, pop, FTP, etc. all will do a reverse lookup.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

edmundliAuthor Commented:
Does it mean that it relate to BIND 9.2 ?

We have other system e.g. sendmail, ftp servers , but it are running fine without having any delay.

Thanks
0
jlevieCommented:
There shouldn't be any difference between a Bind 9 and earlier releases with respect to this. Are the sendmail and FTP servers using this DNS server?


Are the clients that are having the problem on your local network?

For one of the clients with the problem, what happens if you do; 'host that-client-ip'? Is there a long delay or an immediate response?

Likewise, from another system that is using this DNS server for name resolution what response do you get if you do; 'host telnet-server-name' or 'nslookup telnet-server-name'? Is that immediate or slow?

Have you checked the syslog messages on the DNS server for any complaints from Bind when it starts or is running? On Linux any errors would be in /var/log/messages.
0
edmundliAuthor Commented:
I do not what reason that the response was back to normal,
I do not add any hosts, but have all zone-transfers files from others DNS servers.

Is this the reason ?
0
jlevieCommented:
If for some reason there were problems with named accomplishing the zone transfers from other servers there could be problems that could result in DNS timeouts, so yes that could have been the problem. It would depend on what data couldn't be transferred and what data named needed to look up.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.