-
**Describe the bug**
I have been running the latest image of unbound from here along with pihole in two docker containers connected with a user defined bridge network. This setup worked perfectly fo…
-
unable to resolve dns in google cloud
-
### What version of `nebula` are you using?
1.7.2
### What operating system are you using?
Linux ( Arm64 )
### Describe the Bug
When starting nebula, an error is reported:
`ERRO[0000] DNS resol…
-
## Description of the issue
Referencing the `dns` key in YAML does not work when the value is a service alias of another container in the `docker-compose.yml` file.
Sample compose file.
```ya…
-
### Checklist
- [x] Using latest version on the [App Store](http://itunes.apple.com/app/id1156707581)
- [x] Read the [docs](http://blink.sh/docs/)
- [x] Searched for [existing GitHub issues](…
-
### Windows Version
Microsoft Windows [Version 10.0.22621.3007]
### WSL Version
2.0.9.0
### Are you using WSL 1 or WSL 2?
- [X] WSL 2
- [ ] WSL 1
### Kernel Version
5.15.133.1-1…
-
### Issue Description
The DNS resolution in an internal network doesn't work. The DNS server is unreachable.
### Steps to reproduce the issue
Steps to reproduce the issue. Run all commands as root:…
jorti updated
1 month ago
-
Historically I have been setting nonMasqueradeCIDR to a value of my choice (e.g. 10.1.0.0/16) for the internal cluster address allocation to prevent any addresses from a non-private network space (10.…
-
### Describe the bug
Hello, I was using wandb and all of a sudden, I cannot connect to the wandb. It has been working until just a few minutes.
I can still access the wandb dashboard, but either my…
-
**chaosd attack network delay -d eth0 -i 10.8.198.117 -p tcp -s 7005 -l 3s**
```
2021-12-09T15:36:51.507+0800 INFO chaos-daemon-server flush ipset {"request": "ipsets:{name:\"chaos-1…