Fetch unable to resolve.
Hello, I am having problems with fetch and ftp, being unable to resolve any DNS related matters. Like hostnames and stuff. However, nslookup, dig, and those tools still work just fine, i am wondering what the problem could be. See output below. If you need any other info, please let me know, the owner is thinking of having it reinstalled by the data center, but i would like to get to the bottom of this. Sequence of event in the last 4 days: 1. tinydns installed, setup, and totally ready 2. tinydns data copied to a new server, deamontools, tinydns and its stuff uninstalled 3. Nothing done for a day or two 4. Login to setup a mail server, fetch is unable to retrieve ports 5. Try to trouble shoot 6. No means available to get it to work, and here i am. uname -a: charon# uname -a FreeBSD charon.gamershell.com 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 It is a xeon p4 proc. with hyperthreading. Some stats about the IP's that are currently set: charon# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 66.36.241.74 netmask 0xfe00 broadcast 66.36.241.255 inet6 fe80::20d:61ff:fe03:48f3%rl0 prefixlen 64 scopeid 0x1 ether 00:0d:61:03:48:f3 media: Ethernet autoselect (10baseT/UTP full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500 sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552 faith0: flags=8002BROADCAST,MULTICAST mtu 1500 Here is the output i mentioned above, this is what is going wrong.: charon# fetch -v http://google.com/ scheme: [http] user: [] password: [] host: [google.com] port: [0] document: [/] --- google.com:80 looking up google.com fetch: http://google.com/: Host not found charon# nslookup google.com Server: 69-56-211-146.theplanet.com Address: 69.56.211.146 Non-authoritative answer: Name:google.com Addresses: 216.239.57.99, 216.239.37.99, 216.239.39.99 charon# dig google.com ; DiG 8.3 google.com ;; res options: init recurs defnam dnsrch ;; got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 30197 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 0 ;; QUERY SECTION: ;; google.com, type = A, class = IN ;; ANSWER SECTION: google.com. 4m57s IN A 216.239.39.99 google.com. 4m57s IN A 216.239.57.99 google.com. 4m57s IN A 216.239.37.99 ;; AUTHORITY SECTION: google.com. 3d23h59m57s IN NS ns1.google.com. google.com. 3d23h59m57s IN NS ns2.google.com. google.com. 3d23h59m57s IN NS ns3.google.com. google.com. 3d23h59m57s IN NS ns4.google.com. ;; Total query time: 34 msec ;; FROM: charon.gamershell.com to SERVER: 69.56.211.146 ;; WHEN: Thu Feb 26 01:01:44 2004 ;; MSG SIZE sent: 28 rcvd: 148 charon# ftp ftp open ftp.uk.freebsd.org ftp: ftp.uk.freebsd.org: No address associated with hostname ftp open ftp://ftp.uk.freebsd.org/ ftp: ftp://ftp.uk.freebsd.org/: No address associated with hostname ftp exit charon# nslookup ftp.uk.freebsd.org Server: 69-56-211-146.theplanet.com Address: 69.56.211.146 Non-authoritative answer: Name:ftp.plig.net Addresses: 195.40.6.41, 195.40.6.46 Aliases: ftp.uk.freebsd.org charon# cat /etc/resolv.conf nameserver 69.56.211.146 charon# nslookup google.com Server: 69-56-211-146.theplanet.com Address: 69.56.211.146 Non-authoritative answer: Name:google.com Addresses: 216.239.37.99, 216.239.39.99, 216.239.57.99 charon# ping google.com ping: cannot resolve google.com: Unknown host charon# ping 216.239.37.99 PING 216.239.37.99 (216.239.37.99): 56 data bytes 64 bytes from 216.239.37.99: icmp_seq=0 ttl=245 time=2.384 ms 64 bytes from 216.239.37.99: icmp_seq=1 ttl=245 time=2.395 ms 64 bytes from 216.239.37.99: icmp_seq=2 ttl=245 time=2.040 ms 64 bytes from 216.239.37.99: icmp_seq=3 ttl=245 time=2.514 ms 64 bytes from 216.239.37.99: icmp_seq=4 ttl=245 time=1.985 ms ^C --- 216.239.37.99 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.985/2.264/2.514/0.211 ms Thank you, Jan-Willem Regeer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fetch unable to resolve.
On Thursday 26 February 2004 01:11, X-Istence wrote: Hello, I am having problems with fetch and ftp, being unable to resolve any DNS related matters. Like hostnames and stuff. However, nslookup, dig, and those tools still work just fine, i am wondering what the problem could be. See output below. If you need any other info, please let me know, the owner is thinking of having it reinstalled by the data center, but i would like to get to the bottom of this. Sequence of event in the last 4 days: 1. tinydns installed, setup, and totally ready 2. tinydns data copied to a new server, deamontools, tinydns and its stuff uninstalled 3. Nothing done for a day or two You also killed any tinydns/supervise processes? 4. Login to setup a mail server, fetch is unable to retrieve ports 5. Try to trouble shoot 6. No means available to get it to work, and here i am. SNIP So, are you perhaps still using your localhost or your box' IP (former) host to resolve?, e.g. what's in /etc/resolv/conf? I reckon it should use some upstream (your other?) nameserver now. Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fetch unable to resolve.
Danny Pansters wrote: On Thursday 26 February 2004 01:11, X-Istence wrote: Hello, I am having problems with fetch and ftp, being unable to resolve any DNS related matters. Like hostnames and stuff. However, nslookup, dig, and those tools still work just fine, i am wondering what the problem could be. See output below. If you need any other info, please let me know, the owner is thinking of having it reinstalled by the data center, but i would like to get to the bottom of this. Sequence of event in the last 4 days: 1. tinydns installed, setup, and totally ready 2. tinydns data copied to a new server, deamontools, tinydns and its stuff uninstalled 3. Nothing done for a day or two You also killed any tinydns/supervise processes? Yes, tinydns is not found on the server anymore, just dnscache, deamontools is also still there. dnscache was going to be used for the qmail mail server to ease up dns lookups. 4. Login to setup a mail server, fetch is unable to retrieve ports 5. Try to trouble shoot 6. No means available to get it to work, and here i am. SNIP So, are you perhaps still using your localhost or your box' IP (former) host to resolve?, e.g. what's in /etc/resolv/conf? I reckon it should use some upstream (your other?) nameserver now. Output of cat /etc/resolv.conf was posted: charon# cat /etc/resolv.conf nameserver 69.56.211.146 On localhost i installed dnscache to see if that would remedy the problem. All it has done is speed up DNS queries something i was going to add when i was going to compile adn install qMail anyways. Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Jan-Willem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fetch unable to resolve.
On Thursday 26 February 2004 01:25, X-Istence wrote: Danny Pansters wrote: On Thursday 26 February 2004 01:11, X-Istence wrote: Hello, I am having problems with fetch and ftp, being unable to resolve any DNS related matters. Like hostnames and stuff. Reverse DNS not OK? Always tricky business. However, nslookup, dig, and those tools still work just fine, i am wondering what the problem could be. See output below. If you need any other info, please let me know, the owner is thinking of having it reinstalled by the data center, but i would like to get to the bottom of this. HTH Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fetch unable to resolve.
Danny Pansters wrote: On Thursday 26 February 2004 01:25, X-Istence wrote: Danny Pansters wrote: On Thursday 26 February 2004 01:11, X-Istence wrote: Hello, I am having problems with fetch and ftp, being unable to resolve any DNS related matters. Like hostnames and stuff. Reverse DNS not OK? Always tricky business. What do you mean? With hostnames i mean stuff like ftp.uk.freebsd.org, or google.com, which both dont resolve according to fetch, when i do fetch -vv http://google.com/. But when i do nslookup google.com it does work. However, nslookup, dig, and those tools still work just fine, i am wondering what the problem could be. See output below. If you need any other info, please let me know, the owner is thinking of having it reinstalled by the data center, but i would like to get to the bottom of this. HTH Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
