We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not sure what's causing this so I'm asking for your assistance here. I'm using {"type":"standard","location":"dns-vultr-lon-2"}
rms-server.tektonit.ru @176.103.130.130 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61505 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;rms-server.tektonit.ru. IN A ;; ANSWER SECTION: rms-server.tektonit.ru. 3600 IN A 176.103.130.133 ;; Query time: 51 msec ;; SERVER: 176.103.130.130#53(176.103.130.130) ;; WHEN: Sun Feb 02 13:48:41 EET 2020 ;; MSG SIZE rcvd: 67
dig rms-server.tektonit.ru @8.8.8.8 ; <<>> DiG 9.10.6 <<>> rms-server.tektonit.ru @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7150 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;rms-server.tektonit.ru. IN A ;; ANSWER SECTION: rms-server.tektonit.ru. 691 IN A 109.234.156.180 ;; Query time: 50 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sun Feb 02 13:51:14 EET 2020 ;; MSG SIZE rcvd: 67
The text was updated successfully, but these errors were encountered:
I can confirm the above. Just ran a DIG and as a secondary check an nslookup to validate the server address.
Sorry, something went wrong.
No branches or pull requests
Not sure what's causing this so I'm asking for your assistance here. I'm using {"type":"standard","location":"dns-vultr-lon-2"}
AdGuard DNS or AdGuard Home
8.8.8.8
The text was updated successfully, but these errors were encountered: