CURL not working but ping and nslookup yes working with local DNS server Ubuntu16.04nslookup finds ip, but ping doesntCan ping but no DNSLocation of curl dns cache file and location of ubuntu global cache dns fileDNS Works Locally But Not Globallydig/nslookup can't connect but ping canwhy doesn't dig get answer from LAN DNS but ping and nslookup work
Check the validity of a telephone number
Do rainbows show spectral lines from the sun?
Novel where a serial killer lives (almost) forever by swapping bodies
Why did dict.get(key) work but not dict[key]?
How many 1/day spells can a Warlock monster cast?
Is it normal to use a clipper instead of an limiter?
Ask Google to remove thousands of pages from its index after cleaning up from hacked site
What is a good way to challenge an Agonizing Blast Warlock?
Being flown out for an interview, is it ok to ask to stay a while longer to check out the area?
Why was Wouter Basson never charged with crimes against humanity for Project Coast?
How do I plot a 3D surface on top of a 3D plane?
Swap M-x and M-q
Best way to clean car carpet?
Did medieval stores have names?
Cooking octopus: simple boil or broth?
In a shuttle launch, what would have happened if all three SSMEs failed during flight?
Fermat's Last Theorem, mod n
Counter intuitive Bayesian theorem
Multiple processes redirecting to the same file with >
Why do the US media keep claiming that Iran is violating their nuclear deal?
How do I protect myself from bad contracting jobs?
Why is this missile positioned in this odd position? How can it be launched correctly?
What is the difference between turbojet and turbofan engines?
Is it a good idea to contact a candidate?
CURL not working but ping and nslookup yes working with local DNS server Ubuntu16.04
nslookup finds ip, but ping doesntCan ping but no DNSLocation of curl dns cache file and location of ubuntu global cache dns fileDNS Works Locally But Not Globallydig/nslookup can't connect but ping canwhy doesn't dig get answer from LAN DNS but ping and nslookup work
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
We are working with Bind server on Ubuntu 16.04.
We are unable to curl because DNS resolution but ping and nslookup are working from Ubuntu16.04 client.
Client - ping:
root@app-01:~# ping -c1 nightly.dev.project
PING nightly.dev.project (10.110.2.1) 56(84) bytes of data.
64 bytes from 10.110.2.1: icmp_seq=1 ttl=64 time=1.03 ms
--- nightly.dev.project ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.036/1.036/1.036/0.000 ms
Client - nslookup:
root@app-01:~# nslookup nightly.dev.project
Server: 10.110.1.3
Address: 10.110.1.3#53
Name: nightly.dev.project
Address: 10.110.2.1
Client - curl:
root@app-01:~# curl -kv nightly.dev.project
* Rebuilt URL to: nightly.dev.project/
* Trying 10.10.10.24...
* Connected to proxy.dev.com (10.10.10.24) port 8080 (#0)
> GET http://nightly.dev.project/ HTTP/1.1
> Host: nightly.dev.project
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Proxy-Connection: Keep-Alive
< Connection: Keep-Alive
< Content-Length: 1082
<
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (dns_unresolved_hostname)</big>
<BR>
Client - /etc/resolvconf/resolv.conf.d/head :
nameserver 10.110.1.3
nameserver 10.110.1.2
search dev.project
Client - /etc/nsswitch:
#hosts: files mdns4_minimal [NOTFOUND=return] dns
hosts: dns files
networks: files
BIND server - /etc/bind/named.conf.options :
options
#dnssec-validation auto;
dnssec-validation no;
dnssec-enable no;
allow-recursion any; ;
allow-recursion-on any; ;
allow-query any; ;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
dns curl bind url
asked Jul 16 at 14:04
BarBar
31 bronze badge
add a comment
|
We are working with Bind server on Ubuntu 16.04.
We are unable to curl because DNS resolution but ping and nslookup are working from Ubuntu16.04 client.
Client - ping:
root@app-01:~# ping -c1 nightly.dev.project
PING nightly.dev.project (10.110.2.1) 56(84) bytes of data.
64 bytes from 10.110.2.1: icmp_seq=1 ttl=64 time=1.03 ms
--- nightly.dev.project ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.036/1.036/1.036/0.000 ms
Client - nslookup:
root@app-01:~# nslookup nightly.dev.project
Server: 10.110.1.3
Address: 10.110.1.3#53
Name: nightly.dev.project
Address: 10.110.2.1
Client - curl:
root@app-01:~# curl -kv nightly.dev.project
* Rebuilt URL to: nightly.dev.project/
* Trying 10.10.10.24...
* Connected to proxy.dev.com (10.10.10.24) port 8080 (#0)
> GET http://nightly.dev.project/ HTTP/1.1
> Host: nightly.dev.project
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Proxy-Connection: Keep-Alive
< Connection: Keep-Alive
< Content-Length: 1082
<
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (dns_unresolved_hostname)</big>
<BR>
Client - /etc/resolvconf/resolv.conf.d/head :
nameserver 10.110.1.3
nameserver 10.110.1.2
search dev.project
Client - /etc/nsswitch:
#hosts: files mdns4_minimal [NOTFOUND=return] dns
hosts: dns files
networks: files
BIND server - /etc/bind/named.conf.options :
options
#dnssec-validation auto;
dnssec-validation no;
dnssec-enable no;
allow-recursion any; ;
allow-recursion-on any; ;
allow-query any; ;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
dns curl bind url
asked Jul 16 at 14:04
BarBar
31 bronze badge
add a comment
|
We are working with Bind server on Ubuntu 16.04.
We are unable to curl because DNS resolution but ping and nslookup are working from Ubuntu16.04 client.
Client - ping:
root@app-01:~# ping -c1 nightly.dev.project
PING nightly.dev.project (10.110.2.1) 56(84) bytes of data.
64 bytes from 10.110.2.1: icmp_seq=1 ttl=64 time=1.03 ms
--- nightly.dev.project ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.036/1.036/1.036/0.000 ms
Client - nslookup:
root@app-01:~# nslookup nightly.dev.project
Server: 10.110.1.3
Address: 10.110.1.3#53
Name: nightly.dev.project
Address: 10.110.2.1
Client - curl:
root@app-01:~# curl -kv nightly.dev.project
* Rebuilt URL to: nightly.dev.project/
* Trying 10.10.10.24...
* Connected to proxy.dev.com (10.10.10.24) port 8080 (#0)
> GET http://nightly.dev.project/ HTTP/1.1
> Host: nightly.dev.project
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Proxy-Connection: Keep-Alive
< Connection: Keep-Alive
< Content-Length: 1082
<
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (dns_unresolved_hostname)</big>
<BR>
Client - /etc/resolvconf/resolv.conf.d/head :
nameserver 10.110.1.3
nameserver 10.110.1.2
search dev.project
Client - /etc/nsswitch:
#hosts: files mdns4_minimal [NOTFOUND=return] dns
hosts: dns files
networks: files
BIND server - /etc/bind/named.conf.options :
options
#dnssec-validation auto;
dnssec-validation no;
dnssec-enable no;
allow-recursion any; ;
allow-recursion-on any; ;
allow-query any; ;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
dns curl bind url
asked Jul 16 at 14:04
BarBar
31 bronze badge
We are working with Bind server on Ubuntu 16.04.
We are unable to curl because DNS resolution but ping and nslookup are working from Ubuntu16.04 client.
Client - ping:
root@app-01:~# ping -c1 nightly.dev.project
PING nightly.dev.project (10.110.2.1) 56(84) bytes of data.
64 bytes from 10.110.2.1: icmp_seq=1 ttl=64 time=1.03 ms
--- nightly.dev.project ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.036/1.036/1.036/0.000 ms
Client - nslookup:
root@app-01:~# nslookup nightly.dev.project
Server: 10.110.1.3
Address: 10.110.1.3#53
Name: nightly.dev.project
Address: 10.110.2.1
Client - curl:
root@app-01:~# curl -kv nightly.dev.project
* Rebuilt URL to: nightly.dev.project/
* Trying 10.10.10.24...
* Connected to proxy.dev.com (10.10.10.24) port 8080 (#0)
> GET http://nightly.dev.project/ HTTP/1.1
> Host: nightly.dev.project
> User-Agent: curl/7.47.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Proxy-Connection: Keep-Alive
< Connection: Keep-Alive
< Content-Length: 1082
<
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (dns_unresolved_hostname)</big>
<BR>
Client - /etc/resolvconf/resolv.conf.d/head :
nameserver 10.110.1.3
nameserver 10.110.1.2
search dev.project
Client - /etc/nsswitch:
#hosts: files mdns4_minimal [NOTFOUND=return] dns
hosts: dns files
networks: files
BIND server - /etc/bind/named.conf.options :
options
#dnssec-validation auto;
dnssec-validation no;
dnssec-enable no;
allow-recursion any; ;
allow-recursion-on any; ;
allow-query any; ;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 any; ;
;
dns curl bind url
dns curl bind url
asked Jul 16 at 14:04
BarBar
31 bronze badge
asked Jul 16 at 14:04
BarBar
31 bronze badge
asked Jul 16 at 14:04
BarBar
31 bronze badge
asked Jul 16 at 14:04
BarBar
31 bronze badge
asked Jul 16 at 14:04
BarBar
31 bronze badge
31 bronze badge
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
It turns out that the proxy - proxy.dev.com couldn't resolve the DNS record.
Hoping this answer would help to someone who has this unique situation - All the client configurations and DNS machines are right but the proxy not.
answered Jul 18 at 12:41
BarBar
31 bronze badge
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1158682%2fcurl-not-working-but-ping-and-nslookup-yes-working-with-local-dns-server-ubuntu1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It turns out that the proxy - proxy.dev.com couldn't resolve the DNS record.
Hoping this answer would help to someone who has this unique situation - All the client configurations and DNS machines are right but the proxy not.
answered Jul 18 at 12:41
BarBar
31 bronze badge
add a comment
|
It turns out that the proxy - proxy.dev.com couldn't resolve the DNS record.
Hoping this answer would help to someone who has this unique situation - All the client configurations and DNS machines are right but the proxy not.
answered Jul 18 at 12:41
BarBar
31 bronze badge
add a comment
|
It turns out that the proxy - proxy.dev.com couldn't resolve the DNS record.
Hoping this answer would help to someone who has this unique situation - All the client configurations and DNS machines are right but the proxy not.
answered Jul 18 at 12:41
BarBar
31 bronze badge
It turns out that the proxy - proxy.dev.com couldn't resolve the DNS record.
Hoping this answer would help to someone who has this unique situation - All the client configurations and DNS machines are right but the proxy not.
answered Jul 18 at 12:41
BarBar
31 bronze badge
answered Jul 18 at 12:41
BarBar
31 bronze badge
answered Jul 18 at 12:41
BarBar
31 bronze badge
answered Jul 18 at 12:41
BarBar
31 bronze badge
31 bronze badge
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1158682%2fcurl-not-working-but-ping-and-nslookup-yes-working-with-local-dns-server-ubuntu1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
