I setup my WIFI network router with AdGuard DNS to filter out Ads. Works great I even can open Linked in from Russia without VPN. But now I can not access app.logrocket.com
How can I access the app.logrocket.com?
The issue was the AdGuard DNS itself. The "Default" and "Family" DNS consider the logrocket as Ads source. To fix that you should use "Non-filtering" DNS servers
This is answer from "Default" AdGuard DNS
nslookup logrocket.com 94.140.14.14
Server: 94.140.14.14
Address: 94.140.14.14#53
Non-authoritative answer:
Name: logrocket.com
Address: 0.0.0.0
This is answer from "Non-filtering" AdGuard DNS
nslookup logrocket.com 94.140.14.141
Server: 94.140.14.141
Address: 94.140.14.141#53
Non-authoritative answer:
Name: logrocket.com
Address: 104.26.9.185
Name: logrocket.com
Address: 104.26.8.185
Name: logrocket.com
Address: 172.67.75.120
Related
I have a bunch of unbound + nsd, nsd has the reverse zones prescribed and it gives them normally:
nslookup 91.232.162.225 127.0.0.53
225.162.232.91.in-addr.arpa name = mysite.com.
And there are two configs in unbound for addresses on the local subnet:
server:
local-zone: "10.in-addr.arpa.
stub-zone:
name: "10.in-addr.arpa.
stub-addr: 127.0.0.53
and external addresses:
server:
local-zone: "91.in-addr.arpa.
stub-zone:
name: "91.in-addr.arpa.
stub-addr: 127.0.0.53
Everything is fine with local addresses, but for some reason it doesn't work with external addresses
nslookup 91.232.162.225
;; Got SERVFAIL reply from 91.232.162.225, trying next server
** server can't find 10.162.232.91.in-addr.arpa: NXDOMAIN
Maybe someone has faced with this, how to spell stub-zone for external ip correctly.
Thanks
I have a .NET Core API App running in Azure App Services using Windows, but now I want to test it using Linux. The app uses a custom DNS Zone just to map a custom hostname to a specific IP address.
To implement that in my Windows App Service I used the following Application Settings as stated in this page: WEBSITE_DNS_SERVER and WEBSITE_ALT_DNS_SERVER. Although it looks like a workaround, it works pretty well with Windows App Services. But in Linux it seems to have no effect and my app is not resolving the hostname as needed.
How can I use a custom DNS server in Azure App Service with Linux or add a custom hostname like editing the hosts file?
Unlike our App Service Windows, nameresolver.exe is not available and the Application settings for "WEBSITES_ALT_DNS" and "WEBSITES_DNS" do not populate the configuration files within the container. Below are steps are troubleshooting issues for "Alpine" based images since you don’t mention if you are using a Linux container or the default Linux OS.
Install Bind-tools-
apk update
apk add bind-tools
Run Nslookup-
Once bind-tools is installed, you'll see the server that is being used. If bind-tools are not installed, the DNS server will not be shown. Example provided below.
9031977be93a:~# nslookup google.com
Server: 127.0.0.11
Address: 127.0.0.11#53
Non-authoritative answer:
Name: google.com
Address: 216.58.194.174
Name: google.com
Address: 2607:f8b0:4005:801::200e
Update Config file-
To use a different DNS server for testing, update the /etc/resolv.conf file and update the "nameserver" to use a different DNS server. In this example, we're using Googles DNS.
vi /etc/resolv.conf
By default, the following will be in the resolv.conf file.
search reddog.microsoft.com
nameserver 127.0.0.11
options timeout:1 attempts:5 ndots:0cd /etc
If you're not familiar with "vi", press "i" on your keyboard to begin editing the file.
Once you're done, press "esc" and ":wq!" then enter.
search reddog.microsoft.com
nameserver 8.8.8.8
options timeout:1 attempts:5 ndots:0
Running Nslookup again, you'll see the new nameserver being used.
9031977be93a:~# nslookup google.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: google.com
Address: 216.58.194.174
Name: google.com
Address: 2607:f8b0:4005:804::200e
Hardcoding Hostname-
You can also hardcode the IP address for the hostname in question for testing. To do so, you'll need to update the following file.
vi /etc/hosts
Add the IP address that you would like the DNS to point to. In this example, I'm changing the IP for my custom domain.
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.20.0.2 9031977be93a
10.10.10.10 www.polytechniks.com
Save the changes and use "ping" or "traceroute" to see the IP being used. NOTE: Nslookup does NOT use the /etc/hosts file so you will still see the IP address associated with the DNS.
9031977be93a:~# ping www.polytechniks.com
PING www.polytechniks.com (10.10.10.10): 56 data bytes
--- www.polytechniks.com ping statistics ---
8 packets transmitted, 0 packets received, 100% packet loss
9031977be93a:~# traceroute www.polytechniks.com
traceroute to www.polytechniks.com (10.10.10.10), 30 hops max, 46 byte packets
1 172.20.0.1 (172.20.0.1) 0.005 ms 0.004 ms 0.004 ms
I am on ubuntu, and I am running a docker default bridge network. I have containerized versions of zookeeper, kafka, and an app that I wrote that talks to kafka.
I do a:
docker exec -it <my-app id> /bin/bash
Then inside my app's container I run nslookup kafka
/go # nslookup schmafka
nslookup: can't resolve '(null)': Name does not resolve
Name: schmafka
Address 1: 172.20.0.8 docker_kafka_1.docker_default
I do not understand why I get the output "can't resolve '(null)'" and then I get the expected ip address printed out later. I tried to google nslookup and this output message but I cannot figure why this happens.
My /etc/resolv.conf file looks like this:
/go # cat /etc/resolv.conf
search valhalla.local valhalla v
nameserver 127.0.0.11
options ndots:0
This is a bug/oddity in nslookup. The "can't resolve" message is actually about the DNS server in use, not the site you are trying to look up.
For example this query (which tells nslookup to lookup google.com using the 8.8.8.8 DNS server) has no error message:
nslookup google.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8 dns.google
Name: google.com
Address 1: 172.217.164.110 sfo03s18-in-f14.1e100.net
Address 2: 2607:f8b0:4005:80b::200e sfo03s18-in-x0e.1e100.net
But this query (in which the DNS server is "null") does show the "error":
UAP-AC-LR1-BZ.v4.0.42# nslookup google.com
nslookup: can't resolve '(null)': Name does not resolve
Name: google.com
Address 1: 172.217.164.110 sfo03s18-in-f14.1e100.net
Address 2: 2607:f8b0:4005:80b::200e sfo03s18-in-x0e.1e100.net
Admittedly this is misleading/confusing, and really should be fixed in nslookup.
I'm trying to set Google DNS server 8.8.8.8 in Node.js resolve query.
What is the correct way to do so? In command line usually we can do the following:
$ nslookup stackoverflow.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: stackoverflow.com
Address: 151.101.1.69
Address: 151.101.65.69
Address: 151.101.129.69
Address: 151.101.193.69
But its not quite clear how to make same approach in Node.js
require('dns').resolve('stackoverflow.com', function (err, addresses) {
console.log(err, addresses);
});
// => null [ '151.101.1.69', '151.101.65.69', '151.101.129.69', '151.101.193.69' ]
From nodejs doc: https://nodejs.org/api/dns.html#dns_dns_setservers_servers
dns.setServers([
'4.4.4.4',
'[2001:4860:4860::8888]',
]);
You can use following command:
npm config set dns 8.8.8.8
Ping displays unknown host for any domain name.
It worked before this time true!!
Ping works for ip address but fails for domain names.
Can any one help me?
Check what's in /etc/resolv.conf.
If there is no "nameserver" specified, you have to do that in order to resolve domains.
Example:
nameserver dns1.domainname.com
nameserver dns2.domainname.com
or you can use Google's public DNS servers:
nameserver 8.8.8.8
nameserver 8.8.4.4
(1) edit /etc/resolv.conf, add
nameserver dns1.domainname.com
nameserver dns2.domainname.com
(2) another reason may due to /etc/nsswitch.conf
add dns in the hosts: xxx