Hi @Amanda, I'm still looking for a response here. However, I received a new ht2000w modem today, and am having continual DNS errors. Once again, I find that all DNS queries are being rewritten, with the target DNS server completely ignored. For example, I couldn't even get to this website until I reset the modem because of its broken DNS implementation. For example using googles DNS server, a bogus result for this website was being returned, because the DNS query is never actually made to the google DNS server $ dig @8.8.8.8 community.hughesnet.com ; <<>> DiG 9.11.2 <<>> @8.8.8.8 community.hughesnet.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60360 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;community.hughesnet.com. IN A ;; ANSWER SECTION: community.hughesnet.com. 60 IN CNAME c.media-amazon.com. c.media-amazon.com. 60 IN A 13.33.253.147 ;; Query time: 12 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Dec 01 17:17:20 PST 2017 ;; MSG SIZE rcvd: 89 To prove the point, I use a completely bogus DNS server IP which doesn't exist, and the request still succeeds. $ dig @2.3.4.1 community.hughesnet.com ; <<>> DiG 9.11.2 <<>> @2.3.4.1 community.hughesnet.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10027 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;community.hughesnet.com. IN A ;; ANSWER SECTION: community.hughesnet.com. 60 IN CNAME c.media-amazon.com. c.media-amazon.com. 60 IN A 13.33.253.147 ;; Query time: 2 msec ;; SERVER: 2.3.4.1#53(2.3.4.1) ;; WHEN: Fri Dec 01 17:17:45 PST 2017 ;; MSG SIZE rcvd: 89 To further prove that, I use an internal LAN ip address that is bogus, and the request fails, because the request is never routed off my local network for the modem to rewrite. $ dig @192.168.1.32 community.hughesnet.com ; <<>> DiG 9.11.2 <<>> @192.168.1.32 community.hughesnet.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached It is just completely wrong for Hughesnet to mess with DNS like this. It breaks so many things, including your own website.
... View more