Comment 5 for bug 7164

Revision history for this message
In , Tobias Lorenz (tobias-lorenz) wrote : That's not a problem of telnet.

Hi,

I couldn't resolv that host either. But that's not a problem of telnet,
as you can see from the dig command. The host could not be resolved. Was
that server removed or renamed?

$ dig st1.charite.de

; <<>> DiG 9.2.4rc5 <<>> st1.charite.de
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18428
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;st1.charite.de. IN A

;; AUTHORITY SECTION:
charite.de. 3163 IN SOA dns.charite.de.
postmaster.charite.de. 407260001 43200 1800 2419200 3600

;; Query time: 1 msec
;; SERVER: 192.168.100.1#53(192.168.100.1)
;; WHEN: Mon Jul 26 18:56:23 2004
;; MSG SIZE rcvd: 83

Bye,
  Toby