About FirePolice69

an advance test brought up a few errors   Begin testing delegation for hughesnet.com. Name servers listed at parent: ns1.hns.com,ns2.hns.com,ns5.echostar.com Name servers listed at child: ns1.hns.com,ns2.hns.com,ns5.echostar.com No IPv6 name servers found. Parent glue for hughesnet.com found: ns1.hns.com (69.35.42.41) Parent glue for hughesnet.com found: ns2.hns.com (69.35.42.42) Parent glue for hughesnet.com found: ns5.echostar.com (139.85.4.15) Checking glue for ns1.hns.com (69.35.42.41). Checking glue for ns2.hns.com (69.35.42.42). Checking glue for ns5.echostar.com (139.85.4.15). Parent glue for hughesnet.com found: ns1.hns.com (69.35.42.41) Parent glue for hughesnet.com found: ns2.hns.com (69.35.42.42) Parent glue for hughesnet.com found: ns5.echostar.com (139.85.4.15) It is possible to build a referral packet for hughesnet.com that works without EDNS0. Previously used name servers for hughesnet.com: Done testing delegation for hughesnet.com. Nameserver Nameserver ns1.hns.com Begin testing name server ns1.hns.com. Begin testing host ns1.hns.com. Begin testing address 69.35.42.41. Could not find reverse address for 69.35.42.41 (41.42.35.69.in-addr.arpa.). Done testing address 69.35.42.41. Done testing host ns1.hns.com. Name server ns1.hns.com (69.35.42.41) answers queries over UDP. Name server ns1.hns.com (69.35.42.41) answers queries over TCP. Name server ns1.hns.com (69.35.42.41) is not recursive. Name server ns1.hns.com (69.35.42.41) authoritative for hughesnet.com. Done testing name server ns1.hns.com. Nameserver ns2.hns.com Begin testing name server ns2.hns.com. Begin testing host ns2.hns.com. Begin testing address 69.35.42.42. Could not find reverse address for 69.35.42.42 (42.42.35.69.in-addr.arpa.). Done testing address 69.35.42.42. Done testing host ns2.hns.com. Name server ns2.hns.com (69.35.42.42) answers queries over UDP. Name server ns2.hns.com (69.35.42.42) answers queries over TCP. Name server ns2.hns.com (69.35.42.42) is not recursive. Name server ns2.hns.com (69.35.42.42) authoritative for hughesnet.com. Done testing name server ns2.hns.com. Nameserver ns5.echostar.com Begin testing name server ns5.echostar.com. Begin testing host ns5.echostar.com. Begin testing address 139.85.4.15. Reverse for 139.85.4.15 points to an unknown host name (chipzifb.sats.dmz). Done testing address 139.85.4.15. Done testing host ns5.echostar.com. Name server ns5.echostar.com (139.85.4.15) answers queries over UDP. DNS lookup error (connection failed). Name server ns5.echostar.com (139.85.4.15) does not answer queries over TCP. Name server ns5.echostar.com (139.85.4.15) is not recursive. DNS lookup error (connection failed). Name server ns5.echostar.com (139.85.4.15) authoritative for hughesnet.com. Name server ns5.echostar.com (139.85.4.15) not checked for zone transfer of hughesnet.com. Name server ns5.echostar.com (139.85.4.15) not checked for legacy name server ID. Done testing name server ns5.echostar.com. Consistency Begin testing zone consistency for hughesnet.com. SOA at address 69.35.42.41 has serial 776. SOA at address 69.35.42.42 has serial 776. SOA at address 139.85.4.15 has serial 776. All SOA records have consistent serial numbers. All other fields in the SOA record are consistent among all name servers. The listed nameservers for hughesnet.com all report the same set of nameservers. Done testing zone consistency for hughesnet.com. SOA Begin testing SOA parameters for hughesnet.com. Found SOA record for hughesnet.com. Begin testing host ns1.hns.com. Begin testing address 69.35.42.41. Could not find reverse address for 69.35.42.41 (41.42.35.69.in-addr.arpa.). Done testing address 69.35.42.41. Done testing host ns1.hns.com. SOA MNAME for hughesnet.com valid (ns1.hns.com). SOA MNAME for hughesnet.com (ns1.hns.com) listed as NS. SOA MNAME for hughesnet.com (ns1.hns.com) is authoritative. Successful attempt to deliver email for SOA RNAME of hughesnet.com (no_email.hughes.com) using no_email@hughes.com. SOA TTL for hughesnet.com too small (1800) - recommended >= 3600. SOA refresh for hughesnet.com OK (86400) - recommended >= 14400. SOA retry for hughesnet.com OK (14400) - recommended >= 3600. SOA expire for hughesnet.com too small (432000) - recommended >= 604800. SOA expire for hughesnet.com lower than refresh. SOA minimum for hughesnet.com too large (302400) - recommended <= 86400. Done testing SOA parameters for hughesnet.com. Connectivity DNSSEC Begin testing DNSSEC for hughesnet.com. Did not find DS record for hughesnet.com at parent. DNS lookup error (connection failed). Servers for hughesnet.com have consistent extra processing status. Authenticated denial records not found for hughesnet.com. Did not find DNSKEY record for hughesnet.com at child. No DNSKEY(s) found at child, other tests skipped. Done testing DNSSEC for hughesnet.com. Link to this test: ... View more

Here is the results from another site dnscheck.ripe.net   Basic results Advanced results Delegation Nameserver Nameserver ns1.hns.com Could not find reverse address for 69.35.42.41 (41.42.35.69.in-addr.arpa.). Nameserver ns2.hns.com Could not find reverse address for 69.35.42.42 (42.42.35.69.in-addr.arpa.). Nameserver ns5.echostar.com Reverse for 139.85.4.15 points to an unknown host name (chipzifb.sats.dmz). Name server ns5.echostar.com (139.85.4.15) does not answer queries over TCP. Consistency SOA Could not find reverse address for 69.35.42.41 (41.42.35.69.in-addr.arpa.). Connectivity DNSSEC Link to this test: http://dnscheck.ripe.net/?time=1495305671&id=18938783&view=basic&test=standard ... View more

I also came across a website dnscheck.pingdom.com which is supposed to check if the dns is configured properly It did find what it called one warning and what it called one error were found!   Basic View Advanced View   hughesnet.com 2017-05-20 20:19:20   Permalink: Delegation   Everything is fine.   All tests successful in this part, no errors or warnings. Nameserver   ns1.hns.com. Everything is fine.   All tests successful in this part, no errors or warnings. ns2.hns.com. Everything is fine.   All tests successful in this part, no errors or warnings. ns5.echostar.com. Reverse for 139.85.4.15 points to an unknown host name (chipzifb.sats.dmz).   The PTR record for the address points to an unknown host name. Name server ns5.echostar.com (139.85.4.15) does not answer queries over TCP.   The name server failed to answer queries sent over TCP. This is probably due to the name server not correctly set up or due to misconfgured filtering in a firewall. It is a rather common misconception that DNS does not need TCP unless they provide zone transfers - perhaps the name server administrator is not aware that TCP usually is a requirement. Consistency   Everything is fine.   All tests successful in this part, no errors or warnings. SOA   Everything is fine.   All tests successful in this part, no errors or warnings. Connectivity   Everything is fine.   All tests successful in this part, no errors or warnings. DNSSEC   Everything is fine.   All tests successful in this part, no errors or warnings. Dont know if my issues are there or not ... View more

Was wondering would the cable that comcast uses in there hookups be the same for hughesnet. I still havent gotton anywhere and was thinking of moving the modem upstairs to see if the would work but i would have to reroute another cable line and alls i have is comcast cable wire ... View more

ok zte max pro phone sees 5g without a signal downstairs upstairs it sees 5g with 3 bars signal but cant connect to 5g tv downstairs wont connect to 5g sees 5g but without a signal. tablet same deal direct tv box same deal nothing will connect to 5g computer will not connect to 5g but will connect to 2g and be cut off every 3 to 5 minutes which is running on windows 10 a Dell. i brought a friends HP Laptop over to see if it would work and same deal the tablet is on android 5 and the phone on android 6.01 ... View more

Hello and thanks for replying There was no bad weather at all its was sunny and calm. I been having problems soince day one when it was installed which was May 8th When tech support runs there diagnostic they say everything is fine at there end i think its either a bad modem something outside from the installation or since the modem is directly behind the one tv maybe interferience which i cannot see if its that cause i have no slack on the cable to be able to move it anywhere ... View more

I did try calling the installer but he wont come out unless he has an order from hughes to do so so it looks like i am gonna have to go to a friends house whenever i need to use internet till they get this figured out if they ever do ... View more

I really hope either one of them can I just talked to tech support again the act like im lying or something  Can you see how my 5g is not lit up at all with signal but my 2g is the modem is behind this tv here Now from the computer you can see a signal for 5g which is upstairs in bedroom and you see computer connected to 2g now you see i tried connecting computer to 5g and no connection  Finally with computer on 2g i get knocked off every 3 to 10 minutes this is what will show up ... View more

I talked to tech support they fixed that one issue but it didnt help me any i tried the one suggestion that was posted here for me and nothing helped i have no 5g connection just 2g that keeps dropping but because everything on tech support side of things is ok they wont do anything else so i guess im stuck paying 2 years for internet that i may never get to use ... View more