Why does ping to FQDN fails, but dig succeed? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!CNAME to another domain fails on some office networks, why?Setting up a DNS name server for a mass virtual host with Bind9able to dig a hostname but doesn't resolve via ssh or pingMoved DNS and Email Hosting, Now Can't Send/Receive To/From Domains Hosted on Previous HostDNS setup with BINDWhy can host and nslookup resolve a name but dig cannot?How to correctly configure nameserversWhy does dig succeed if I add an SOA query and fail when I do not?Cannot find solution to “One or more of your nameservers did not return any of your NS records.” on intoDNS sitebind dns resolution failure through cname chain

Sum letters are not two different

Crossing US/Canada Border for less than 24 hours

What was the first language to use conditional keywords?

Why weren't discrete x86 CPUs ever used in game hardware?

What is a fractional matching?

What is this clumpy 20-30cm high yellow-flowered plant?

Disembodied hand growing fangs

An adverb for when you're not exaggerating

How does light 'choose' between wave and particle behaviour?

How to tell that you are a giant?

How could we fake a moon landing now?

How were pictures turned from film to a big picture in a picture frame before digital scanning?

Why should I vote and accept answers?

Is it fair for a professor to grade us on the possession of past papers?

Illegal assignment from sObject to Id

Maximum summed subsequences with non-adjacent items

How do I find out the mythology and history of my Fortress?

Should I use a zero-interest credit card for a large one-time purchase?

What is the topology associated with the algebras for the ultrafilter monad?

How to install press fit bottom bracket into new frame

How to react to hostile behavior from a senior developer?

Most bit efficient text communication method?

How to compare two different files line by line in unix?

How does the math work when buying airline miles?



Why does ping to FQDN fails, but dig succeed?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!CNAME to another domain fails on some office networks, why?Setting up a DNS name server for a mass virtual host with Bind9able to dig a hostname but doesn't resolve via ssh or pingMoved DNS and Email Hosting, Now Can't Send/Receive To/From Domains Hosted on Previous HostDNS setup with BINDWhy can host and nslookup resolve a name but dig cannot?How to correctly configure nameserversWhy does dig succeed if I add an SOA query and fail when I do not?Cannot find solution to “One or more of your nameservers did not return any of your NS records.” on intoDNS sitebind dns resolution failure through cname chain



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















When I try to ping a certain FQDN, I fail:



$ ping test-customer-1.clients.jsonar.com
ping: test-customer-1.clients.jsonar.com: Name or service not known


However, dig et al. succeeds:



$ dig test-customer-1.clients.jsonar.com

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> test-customer-1.clients.jsonar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57830
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test-customer-1.clients.jsonar.com. IN A

;; ANSWER SECTION:
test-customer-1.clients.jsonar.com. 3119 IN CNAME _r1.clients.jsonar.com.
_r1.clients.jsonar.com. 3119 IN CNAME _w1.clients.jsonar.com.
_w1.clients.jsonar.com. 3119 IN A 3.209.217.53

;; Query time: 15 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Fri Apr 12 15:44:21 PDT 2019
;; MSG SIZE rcvd: 115

$ nslookup test-customer-1.clients.jsonar.com.
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
test-customer-1.clients.jsonar.com canonical name = _r1.clients.jsonar.com.
_r1.clients.jsonar.com canonical name = _w1.clients.jsonar.com.
Name: _w1.clients.jsonar.com
Address: 3.209.217.53

$ host test-customer-1.clients.jsonar.com
test-customer-1.clients.jsonar.com is an alias for _r1.clients.jsonar.com.
_r1.clients.jsonar.com is an alias for _w1.clients.jsonar.com.
_w1.clients.jsonar.com has address 3.209.217.53


Files:



$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.99
nameserver 8.8.8.8

$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp0s31f6"
UUID="cf566dc0-de91-497d-a045-560fddfbaf3e"
DEVICE="enp0s31f6"
ONBOOT="yes"
DNS1=8.8.8.8

$ cat /etc/nsswitch.conf | grep hosts
#hosts: db files nisplus nis dns
#hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns myhostname


Edits:



$ getent hosts test-customer-1.clients.jsonar.com
$ echo $?
2
# According to the man page, exit code 2 means:
# One or more supplied key could not be found in the database


Pinging from Linux machines fail, but succeed from Windows machines.










share|improve this question
























  • What does 'host test-customer-1.clients.jsonar.com' result

    – Jacob Evans
    Apr 13 at 0:55











  • Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

    – Zoredache
    Apr 13 at 5:02











  • I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

    – Thomas
    Apr 13 at 17:13






  • 1





    1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

    – Patrick Mevzek
    Apr 14 at 3:29











  • The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

    – boardrider
    Apr 15 at 17:45


















0















When I try to ping a certain FQDN, I fail:



$ ping test-customer-1.clients.jsonar.com
ping: test-customer-1.clients.jsonar.com: Name or service not known


However, dig et al. succeeds:



$ dig test-customer-1.clients.jsonar.com

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> test-customer-1.clients.jsonar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57830
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test-customer-1.clients.jsonar.com. IN A

;; ANSWER SECTION:
test-customer-1.clients.jsonar.com. 3119 IN CNAME _r1.clients.jsonar.com.
_r1.clients.jsonar.com. 3119 IN CNAME _w1.clients.jsonar.com.
_w1.clients.jsonar.com. 3119 IN A 3.209.217.53

;; Query time: 15 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Fri Apr 12 15:44:21 PDT 2019
;; MSG SIZE rcvd: 115

$ nslookup test-customer-1.clients.jsonar.com.
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
test-customer-1.clients.jsonar.com canonical name = _r1.clients.jsonar.com.
_r1.clients.jsonar.com canonical name = _w1.clients.jsonar.com.
Name: _w1.clients.jsonar.com
Address: 3.209.217.53

$ host test-customer-1.clients.jsonar.com
test-customer-1.clients.jsonar.com is an alias for _r1.clients.jsonar.com.
_r1.clients.jsonar.com is an alias for _w1.clients.jsonar.com.
_w1.clients.jsonar.com has address 3.209.217.53


Files:



$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.99
nameserver 8.8.8.8

$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp0s31f6"
UUID="cf566dc0-de91-497d-a045-560fddfbaf3e"
DEVICE="enp0s31f6"
ONBOOT="yes"
DNS1=8.8.8.8

$ cat /etc/nsswitch.conf | grep hosts
#hosts: db files nisplus nis dns
#hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns myhostname


Edits:



$ getent hosts test-customer-1.clients.jsonar.com
$ echo $?
2
# According to the man page, exit code 2 means:
# One or more supplied key could not be found in the database


Pinging from Linux machines fail, but succeed from Windows machines.










share|improve this question
























  • What does 'host test-customer-1.clients.jsonar.com' result

    – Jacob Evans
    Apr 13 at 0:55











  • Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

    – Zoredache
    Apr 13 at 5:02











  • I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

    – Thomas
    Apr 13 at 17:13






  • 1





    1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

    – Patrick Mevzek
    Apr 14 at 3:29











  • The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

    – boardrider
    Apr 15 at 17:45














0












0








0


1






When I try to ping a certain FQDN, I fail:



$ ping test-customer-1.clients.jsonar.com
ping: test-customer-1.clients.jsonar.com: Name or service not known


However, dig et al. succeeds:



$ dig test-customer-1.clients.jsonar.com

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> test-customer-1.clients.jsonar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57830
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test-customer-1.clients.jsonar.com. IN A

;; ANSWER SECTION:
test-customer-1.clients.jsonar.com. 3119 IN CNAME _r1.clients.jsonar.com.
_r1.clients.jsonar.com. 3119 IN CNAME _w1.clients.jsonar.com.
_w1.clients.jsonar.com. 3119 IN A 3.209.217.53

;; Query time: 15 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Fri Apr 12 15:44:21 PDT 2019
;; MSG SIZE rcvd: 115

$ nslookup test-customer-1.clients.jsonar.com.
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
test-customer-1.clients.jsonar.com canonical name = _r1.clients.jsonar.com.
_r1.clients.jsonar.com canonical name = _w1.clients.jsonar.com.
Name: _w1.clients.jsonar.com
Address: 3.209.217.53

$ host test-customer-1.clients.jsonar.com
test-customer-1.clients.jsonar.com is an alias for _r1.clients.jsonar.com.
_r1.clients.jsonar.com is an alias for _w1.clients.jsonar.com.
_w1.clients.jsonar.com has address 3.209.217.53


Files:



$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.99
nameserver 8.8.8.8

$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp0s31f6"
UUID="cf566dc0-de91-497d-a045-560fddfbaf3e"
DEVICE="enp0s31f6"
ONBOOT="yes"
DNS1=8.8.8.8

$ cat /etc/nsswitch.conf | grep hosts
#hosts: db files nisplus nis dns
#hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns myhostname


Edits:



$ getent hosts test-customer-1.clients.jsonar.com
$ echo $?
2
# According to the man page, exit code 2 means:
# One or more supplied key could not be found in the database


Pinging from Linux machines fail, but succeed from Windows machines.










share|improve this question
















When I try to ping a certain FQDN, I fail:



$ ping test-customer-1.clients.jsonar.com
ping: test-customer-1.clients.jsonar.com: Name or service not known


However, dig et al. succeeds:



$ dig test-customer-1.clients.jsonar.com

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> test-customer-1.clients.jsonar.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57830
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;test-customer-1.clients.jsonar.com. IN A

;; ANSWER SECTION:
test-customer-1.clients.jsonar.com. 3119 IN CNAME _r1.clients.jsonar.com.
_r1.clients.jsonar.com. 3119 IN CNAME _w1.clients.jsonar.com.
_w1.clients.jsonar.com. 3119 IN A 3.209.217.53

;; Query time: 15 msec
;; SERVER: 192.168.1.99#53(192.168.1.99)
;; WHEN: Fri Apr 12 15:44:21 PDT 2019
;; MSG SIZE rcvd: 115

$ nslookup test-customer-1.clients.jsonar.com.
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
test-customer-1.clients.jsonar.com canonical name = _r1.clients.jsonar.com.
_r1.clients.jsonar.com canonical name = _w1.clients.jsonar.com.
Name: _w1.clients.jsonar.com
Address: 3.209.217.53

$ host test-customer-1.clients.jsonar.com
test-customer-1.clients.jsonar.com is an alias for _r1.clients.jsonar.com.
_r1.clients.jsonar.com is an alias for _w1.clients.jsonar.com.
_w1.clients.jsonar.com has address 3.209.217.53


Files:



$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.1.99
nameserver 8.8.8.8

$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp0s31f6"
UUID="cf566dc0-de91-497d-a045-560fddfbaf3e"
DEVICE="enp0s31f6"
ONBOOT="yes"
DNS1=8.8.8.8

$ cat /etc/nsswitch.conf | grep hosts
#hosts: db files nisplus nis dns
#hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts: files dns myhostname


Edits:



$ getent hosts test-customer-1.clients.jsonar.com
$ echo $?
2
# According to the man page, exit code 2 means:
# One or more supplied key could not be found in the database


Pinging from Linux machines fail, but succeed from Windows machines.







domain-name-system ping host dig






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 9 hours ago







boardrider

















asked Apr 12 at 23:21









boardriderboardrider

312415




312415












  • What does 'host test-customer-1.clients.jsonar.com' result

    – Jacob Evans
    Apr 13 at 0:55











  • Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

    – Zoredache
    Apr 13 at 5:02











  • I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

    – Thomas
    Apr 13 at 17:13






  • 1





    1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

    – Patrick Mevzek
    Apr 14 at 3:29











  • The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

    – boardrider
    Apr 15 at 17:45


















  • What does 'host test-customer-1.clients.jsonar.com' result

    – Jacob Evans
    Apr 13 at 0:55











  • Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

    – Zoredache
    Apr 13 at 5:02











  • I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

    – Thomas
    Apr 13 at 17:13






  • 1





    1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

    – Patrick Mevzek
    Apr 14 at 3:29











  • The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

    – boardrider
    Apr 15 at 17:45

















What does 'host test-customer-1.clients.jsonar.com' result

– Jacob Evans
Apr 13 at 0:55





What does 'host test-customer-1.clients.jsonar.com' result

– Jacob Evans
Apr 13 at 0:55













Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

– Zoredache
Apr 13 at 5:02





Or more interestingly, what does getent hosts test-customer-1.clients.jsonar.com.

– Zoredache
Apr 13 at 5:02













I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

– Thomas
Apr 13 at 17:13





I guess the DNS server at 192.168.1.99 cannot resolve the address. You can verify that with 'dig test-customer-1.clients.jsonar.com @192.168.1.99. If that is the case fix the DNS server at 192.168.1.99` or just use `8.8.8.8'.

– Thomas
Apr 13 at 17:13




1




1





1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

– Patrick Mevzek
Apr 14 at 3:29





1) ping is not a tool to use to debug troubleshooting problems, only dig fits for that purpose and 2) never use dig without the @ option otherwise you do not really control which nameserver you query.

– Patrick Mevzek
Apr 14 at 3:29













The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

– boardrider
Apr 15 at 17:45






The DNS module on 192.168.1.99 (it's a FortiGate firewall box) can resolve only addresses on the .local LAN. Any external name resolutions are forwarded to FortiNet DNS servers. As you can see in the question, @Thomas, /etc/resolv.conf includes 8.8.8.8.

– boardrider
Apr 15 at 17:45











1 Answer
1






active

oldest

votes


















0














Turns out the problem was caused by quite a bizarre misconfiguration:
test-customer-1.clients.jsonar.com record in DNS was NS instead of an A record.
(Seems that Windows doesn't care, which is why pings from a Windows machine were successful, but *nix treats this misconfiguration (correctly) as a possible security breach, and fails the pings).



Once test-customer-1.clients.jsonar.com was registered in DNS with an A record, the issue was resolved.






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    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/3.0/"u003ecc by-sa 3.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
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962872%2fwhy-does-ping-to-fqdn-fails-but-dig-succeed%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









    0














    Turns out the problem was caused by quite a bizarre misconfiguration:
    test-customer-1.clients.jsonar.com record in DNS was NS instead of an A record.
    (Seems that Windows doesn't care, which is why pings from a Windows machine were successful, but *nix treats this misconfiguration (correctly) as a possible security breach, and fails the pings).



    Once test-customer-1.clients.jsonar.com was registered in DNS with an A record, the issue was resolved.






    share|improve this answer



























      0














      Turns out the problem was caused by quite a bizarre misconfiguration:
      test-customer-1.clients.jsonar.com record in DNS was NS instead of an A record.
      (Seems that Windows doesn't care, which is why pings from a Windows machine were successful, but *nix treats this misconfiguration (correctly) as a possible security breach, and fails the pings).



      Once test-customer-1.clients.jsonar.com was registered in DNS with an A record, the issue was resolved.






      share|improve this answer

























        0












        0








        0







        Turns out the problem was caused by quite a bizarre misconfiguration:
        test-customer-1.clients.jsonar.com record in DNS was NS instead of an A record.
        (Seems that Windows doesn't care, which is why pings from a Windows machine were successful, but *nix treats this misconfiguration (correctly) as a possible security breach, and fails the pings).



        Once test-customer-1.clients.jsonar.com was registered in DNS with an A record, the issue was resolved.






        share|improve this answer













        Turns out the problem was caused by quite a bizarre misconfiguration:
        test-customer-1.clients.jsonar.com record in DNS was NS instead of an A record.
        (Seems that Windows doesn't care, which is why pings from a Windows machine were successful, but *nix treats this misconfiguration (correctly) as a possible security breach, and fails the pings).



        Once test-customer-1.clients.jsonar.com was registered in DNS with an A record, the issue was resolved.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 9 hours ago









        boardriderboardrider

        312415




        312415



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962872%2fwhy-does-ping-to-fqdn-fails-but-dig-succeed%23new-answer', 'question_page');

            );

            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







            Popular posts from this blog

            Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

            Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

            Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020