Facebook DNS

[Hopsasa]

I was just testing around with some DNS stuff. I then decided to try some of those DNS check tools. On both facebook and reddit i got warnings and errors. I dont know if this is legit or important? 

 

Heres my facebook.com report : http://dnscheck.pingdom.com/troubleshooting.php?domain=facebook.com&timestamp=1409934679

[EliasNM]

what are you expecting exactly from the tests? Is the access fine via www..com just not working in testing? I doubt its DNS fault if you can access fine via web, I'm willing to bet those nameservers are not meant for public access.

[Hopsasa]

I can access both websites, but it could be fishing without me even noticing it? What are your results?

[EliasNM]

I can access both websites, but it could be fishing without me even noticing it? What are your results?

That doesn't explain the fail in nameserver communication though. Nameservers are servers that translate IP to a domain name and the one you think you are connecting to is the back door not the front one, in this case Facebook.com so you are fine, there may be test out there that address your concern just not DNS testing. Mines were the same, I think most others are also the same.

[Hopsasa]

That doesn't explain the fail in nameserver communication though. Nameservers are servers that translate IP to a domain name and the one you think you are connecting to is the back door not the front one, in this case Facebook.com so you are fine, there may be test out there that address your concern just not DNS testing. Mines were the same, I think most others are also the same.

Well then i feel great the thing i was worried about was the the things marked yellow ;D

 

edit: Delivery over IPv4 to dns@facebook.com could not be done. thats the thing i was mainly concerned about

[EliasNM]

Well then i feel great the thing i was worried about was the the things marked yellow ;D

 

edit: Delivery over IPv4 to dns@facebook.com could not be done. thats the thing i was mainly concerned about

SOA has to do with them too, DNS on your end is fine, if this was your website testing then you need to worry, a SOA record needs to be present technically, but because its a corporate handled website SOA records are probably hosted on a different nameserver hence that error as well. Its for their protection not yours essentially. Test other DNS and report back if results differ, doubt they will.

[Hopsasa]

SOA has to do with them too, DNS on your end is fine, if this was your website testing then you need to worry, a SOA record needs to be present technically, but because its a corporate handled website SOA records are probably hosted on a different nameserver hence that error as well. Its for their protection not yours essentially. Test other DNS and report back if results differ, doubt they will.

 

SOA has to do with them too, DNS on your end is fine, if this was your website testing then you need to worry, a SOA record needs to be present technically, but because its a corporate handled website SOA records are probably hosted on a different nameserver hence that error as well. Its for their protection not yours essentially. Test other DNS and report back if results differ, doubt they will.

tested some other websites. Here is komplett.dk a danish computer seller. http://dnscheck.pingdom.com/troubleshooting.php?domain=komplett.dk&timestamp=1445356000&view=1.

 

edit: this one is not owned by a giant corporation. I know this is probably completely normal. It would be worrying if it was my own website. Checked that no problems