Timeline for Strange issue with curl/lynx and non resolving domains
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2016 at 1:49 | history | edited | Jeff Schaller♦ |
edited tags
|
|
| Nov 19, 2012 at 20:05 | vote | accept | Steve Abraham | ||
| Nov 19, 2012 at 18:28 | answer | added | mreithub | timeline score: 5 | |
| Nov 19, 2012 at 17:29 | comment | added | Steve Abraham | @mreithub resolv.conf doesn't seem to have a search line - just the following: nameserver 78.31.111.10 nameserver 78.31.104.43 options timeout:1 options rotate options attempts:1 | |
| Nov 19, 2012 at 17:26 | comment | added | mreithub |
There might be a search *****.co.uk line in your /etc/resolv.conf that you might want to remove (unless you depend on the domain expansion)
|
|
| Nov 19, 2012 at 17:24 | comment | added | Steve Abraham | @mreithub: ** server can't find jksodf89s9df9sudfisdf.com: NXDOMAIN | |
| Nov 19, 2012 at 17:23 | comment | added | Steve Abraham | @derobert:78.31.104.52 jksodf89s9df9sudfisdf.com.*****.co.uk - so it's appending my own domain name to the end of the non existant domain... I've got wildcard DNS set up, so that certainly explains why it's ending up on localhost. I've no idea how to prevent that though, other than removing the wildcard DNS... | |
| Nov 19, 2012 at 17:02 | comment | added | derobert |
And also getent hosts jksodf89s9df9sudfisdf.com to see what the libc resolver thinks.
|
|
| Nov 19, 2012 at 17:01 | comment | added | mreithub |
What does nslookup jksodf89s9df9sudfisdf.com say? I think that it's a DNS issue as Apache itself has absolutely nothing to do with what curl/lynx/wget/... do to resolve hosts.
|
|
| Nov 19, 2012 at 16:43 | review | First posts | |||
| Nov 19, 2012 at 17:27 | |||||
| Nov 19, 2012 at 16:24 | history | asked | Steve Abraham | CC BY-SA 3.0 |